Commit timeout query - JDBC
Ours is a java based front-ending application. In this, we are using oracle 11g JDBC driver to connect to ORACLE. As per JDBC specification, we are using query timeout parameter to specify the maximum threshold time a thread can be kept waiting for query to finish. But the same is available at query execution level only i.e. on statement object or on preparedstatement object. But we need similar functionality at connection level. To be more precise, any call to ORACLE from JDBC should not take more time than specified limit, otherwise the same calls should be cancelled. E.g. if commit is taking very high time and we don’t want our thread to be kept waiting for commit. In this case, probably on encountering timeout, we may either rollback the transaction or just close the connection,
Is the same is supported anyhow in JDBC or in ORACLE which can be configured from front-ending application?
There is a JDBC forum which is more appropriate for this.
And IMHO a commit call is something that you do NOT want to control a timeout on. Maybe in gross limits but not small limits. If I had a commit that was in fact normally taking a long amount of time I would look to the statements being executed in the transactions as being incorrect or too big. And refactor there.
Similar Messages
-
Is there any way to set read timeout on JDBC connection?
When the network connectivity between the machine
where Database is running and where the application is running breaks,
the query executed using the old connection handle is not timing out.
Is there any way to set read timeout on JDBC connection. ?
FYI, Oracle JDBC thin Driver is used in our application.Set the tuning parameters with Embedded OC4J Server Preferences>Current Workspace>Data Sources>jdev-connection-DBConnection1 node.
Select the Tuning tab.
The Inactivity Timeout parameter specifies the number of secs of inactivity after which a connection gets disconnected. -
How to notify in case SQL query(JDBC sender adapter) does not fetch records
hi,
How can we notify(by alerts or something) in case SQL query(JDBC sender adapter) does not fetch records? In channels logs it only says processing started & finished(no message is created for same).
Thanks,
MayankHi,
1 ) What is exact audit log message ?
2) Try fetching the count in SQL statement if there are any valid records it will give the count.
May for testing you can use <TEST> in update statement.
3) Have you used taskTimeout parameter ?
4) Are multiple channels polling on same table ?
regards
Ganga -
Why does JDBC make me commit a query?
I was working with two DB2 database connections, A and B, and performed the following logic:
Turned off AutoCommit for A and B
Updated A
Updated B
Committted A
Rolled back B
Selected from A
Selected from B
Updated A
Committed A
Closed Connection A
Closed Connection B
Everything worked well until I tried to close Connection B. It threw a SQL Exception with the description "invalid transaction state". I read online that this means you are trying to close a connection with uncommitted data. It didn't make sense because the only thing I had done since rolling back was SELECT. When I tried it with a rollback or commit immediately before closing the connection, it worked. Any ideas why it would make me commit a SELECT? Is this just an unintended bug or could they have implemented it like this on purpose?I also first was wondering why a select should be committed.
But also a select can cause locks that influence other connections. How, depends on the isolation level you set. For example SERIALIZABLE would block inserts by another connection that would change your retrieval in case you repeat it.
To make the DBMS know that after your retrieval your processing of these data is done - no changes following - you must end the transaction by commit (or rollback - would be the same here since you've done no changes). -
by connection is getting lost very soon my data is very larger i want to specify query timeout. so that when connection is lost it can restsrt immediately. i want to do this in connectiion of oracle. progrmatically
There is a JDBC forum which is more appropriate for this.
And IMHO a commit call is something that you do NOT want to control a timeout on. Maybe in gross limits but not small limits. If I had a commit that was in fact normally taking a long amount of time I would look to the statements being executed in the transactions as being incorrect or too big. And refactor there. -
I have an urgent query . I have written a java code on microsoft platform that talks with SQL server 2000 hosted on windows200 machine in a network using JDBCODBC driver wothou using a Data source name.
But this same code when i try to run on mandrake linux throws an exception as
java.sql.SQLException: [unixODBC] [Driver Manager] Data source name not found,
and no default driver specified.MS provides a JDBC driver for MSSQL 2000, go to there site and download it.
-
Auto-Commit and Pooled JDBC Connections
Forum Members,
If I am using Oracle Pooled JDBC Connections in the OC4J container is auto-commit set to "true" by default?
If I set auto-commit to "false" and then close the logical connection, when that connection is handed out again on a later call to getConnection(), is auto-commit automatically set back to "true"?
Thanks,
RichardRichard,
Pardon me if I am stating the obvious, but you could test that in your code by invoking the getAutoCommit() method in interface java.sql.Connection.
My experience (with OC4J stand-alone versions up to -- and including -- 10.1.2) is that the behaviour depends on which data source you have configured. For example, if you have defined an "ejb-location" attribute in your "data-sources.xml" file, and you use that as your JNDI lookup for your data source, then OC4J handles transactions and you shouldn't deal with "auto-commit" at all. See the following post for more details:
Re: OC4J 10.1.3 Preview 4 - Global transaction active
But if you have defined a "location" attribute and use that, then you do need to handle transactions explicitly.
Hope this helps.
Good Luck,
Avi. -
EntityManager.setFlushMode(COMMIT) Vs. Query.setFlushMode(COMMIT)
[P-331 of EJB3 In Action Book] states:
"By default, the database flush mode is set to AUTO. This means that the Entity-Manager performs a flush operation automatically as needed.
In general, this occurs at the end of a transaction for transaction-scoped EntityManagers and when the persistence context is closed for
application-managed or extendedscope EntityManagers. In addition, if entities with pending changes are used in a query, the persistence
provider will flush changes to the database before executing the query.If the flush mode is set to COMMIT, the persistence provider will
only synchronize with the database when the transaction commits.However, you should be careful with this, as it will be your responsibility
to synchronize entity state with the database before executing a query. If you dont do this and an EntityManager query returns stale
entities from the database, the application can wind up in an inconsistent state."
[P-353 EJB3 In Action Book] states:
"If the Query is set to FlushModeType.COMMIT, the effect of updates made to entities in the persistence context is not defined
by the specification, and the actual behavior is implementation specific".
So setting the flush mode as COMMIT on EntityManager and Query have different results..Right ??I would say try before you believe, but this is not the first time you post a blatant mistake/contradiction taken from this book, isn't it? Perhaps it is time to move on the a better, more dependable resource, or keep using this book and research a little further when you find something that seems backwards to you. I have personally recommended "Enterprise Javabeans 3.0" by O'Reilly many times before, and I still say it is one of the best resources on the subject right now.
-
Remove comma in query output from Char used as KF
Hello Friends,
To be able to display a characteristic in a particular way I used formula variable and displayed it as Key Figure in the query output. By doing this I am getting the output in the required format, but only problem is that the value is being displayed with commas. As it is an order number, I want to display it without commas.
I don't want to use VB as the query is to be published in web also.
Please suggest if there is any way to achieve this.
Thanks in advance.
PraveenHey Praveen, there's a few ways to skin this cat. The simplest method is to make sure that the user parameters in SU3 don't have commas for numbers. The problem is that this is a global setting so you won't get commas for other numbers in which you may want commas. Also, you'd have to make sure your replacement variable was defined as type "number". The other options include using VBA in BEx, and/or Table Interface in the Web. If you are using BW 3.5, you can use XSLT to render a table with and not have commas for that value by using the XML Query Result Set Item. Hope that helps,
Prakash -
Timeout querying LDAP groups from BPM Workspace Administration page
I already configured my server to use Active Directory instead the Weblogic embedded LDAP to users authentication in the BPM Workspace.
When I go to [Weblogic Console / Security Realms / myrealm / Users and Groups / Groups] the console shows correctly all the AD groups after a 20 secs aprox, but when I try to assign some group to a role using the BPM Workspace Administration menu, the app only show users in the search pop up, if I search usign "All" or "Groups" filter I always get this error:
ORABPEL-10592
Identity Service soap error.
BPMIdentityService encountered soap error in method invoke for with fault "javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: miserver.com:389 [Root exception is java.net.ConnectException: Connection timed out]]".
Ensure that the soap message is properly formed and has all necessary attributes and elements. Contact oracle support if error is not fixable.
at oracle.bpel.services.identity.client.IdentityServiceSOAPClient.invoke(IdentityServiceSOAPClient.java:265)
at oracle.bpel.services.identity.client.IdentityServiceSOAPClient.searchGroups(IdentityServiceSOAPClient.java:391)
at oracle.bpel.services.identity.client.AbstractIdentityServiceClient.searchGroups(AbstractIdentityServiceClient.java:514)
at oracle.bpel.worklistapp.dc.idbrowser.beans.model.identity.UnrestrictedIDSearcher.searchGroups(UnrestrictedIDSearcher.java:65)
at oracle.bpel.worklistapp.dc.idbrowser.beans.model.IdentityBrowserModel.executeSearch(IdentityBrowserModel.java:265)
at oracle.bpel.worklistapp.dc.idbrowser.beans.view.IdentityBrowserView.executeSearch(IdentityBrowserView.java:308)
at oracle.bpel.worklistapp.dc.idbrowser.beans.controller.IdentityBrowserController.executeSearch(IdentityBrowserController.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.el.parser.AstValue.invoke(AstValue.java:157)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53)
at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1259)
at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:97)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94)
at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:91)
at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:148)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94)
at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:97)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94)
at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:91)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94)
at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:97)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:90)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:309)
at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:94)
at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:91)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:812)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:292)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:414)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:414)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)It seems like the long response time from AD is closing the connection, but I can find where to configure the timeout for workspace app. In my Provider specific settings for AD provider I checked "Keep Alive Enabled" but doesn't work.
Any ideas about this?, I'm using Oracle SOA Suite 11gR3Hello Martin,
Did you check it on apex.oracle.com because I just did and didn’t encounter the same problem.
Regards,
Arie.
♦ Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.
♦ Author of Oracle Application Express 3.2 – The Essentials and More -
Hi All,
We are facing a problem in BPM with S/A Bridge.
In the BPM we are synchronously calling multiple
stored procedures. Each of these stored procedures
will take 10-1200Secs for sending back the reponse.
Last step in the BPM is to close the S/A Bridge.
But maximum time-delay allowed in XI between
opening and closing S/A bridge is only 100sec.
(Param - CHECK_FOR_ASYNC_RESPONSE_TIMEOUT)
So we are unable close the bridge. It is getting
time-out.
Is there any way to overcome this limitation ??
We are using XI SP15.
Thanks in Advance
ChemmanzHi Chemmanz,
The settings can be done SXMB_ADM -> Integration Engine Config -> Change Specific Config -> Add a new entry
Check the Category SA_COMM, see the help for its parameters.
By default the time out setting is 60 seconds and the maximum allowed is 1000 seconds.
Regards,
Abhy -
Timestem and jdbc Query Timeout
hi all,
i have install timesten on one computer and configure there Query Timeout like This:
SQLQueryTimeout = 80
and i have JBoss Application Server on another computer and timesten client.
i've timesten-xa-ds.xml configuration file configured like this :
<set-tx-query-timeout>
<query-timeout>50000</query-timeout>
<set-tx-query-timeout>
and when i tryed to execute sql command i get an error:
14:19:13,342 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: S1000
14:19:13,344 ERROR [JDBCExceptionReporter] [TimesTen][TimesTen 6.0.4 CLIENT]Query Timeout must be numeric, greater than or equal to 0, and less than the Network Timeout
14:19:13,346 ERROR [STDERR] javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not execute query
14:19:13,346 ERROR [STDERR] at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:567)
14:19:13,346 ERROR [STDERR] at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:56)
14:19:13,347 ERROR [STDERR] at com.magti.businesslayer.ejb3Fasade.srvprov.MobileServiceFasadeBean.simChange(MobileServiceFasadeBean.java:1381)
can anybody help me ? :(We are execute some tests and we got this mistake
java.sql.SQLException: [TimesTen][TimesTen 7.0.1.0.0 CLIENT]Query Timeout must be numeric; if the Network Timeout is non-zero, the Query Timeout must be greater than zero and less than the Network Timeout, else if the Network Timeout is zero, the Query Timeout must be greater than or equal to zero.
at com.timesten.jdbc.JdbcOdbc.createSQLException(JdbcOdbc.java:3186)
at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:3320)
at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:3285)
at com.timesten.jdbc.JdbcOdbc.SQLSetStmtOption(JdbcOdbc.java:2555)
at com.timesten.jdbc.JdbcOdbcStatement.setStmtOption(JdbcOdbcStatement.java:1889)
at com.timesten.jdbc.JdbcOdbcStatement.setQueryTimeout (JdbcOdbcStatement.java:714)
at org.hibernate.jdbc.AbstractBatcher.closeQueryStatement(AbstractBatcher.java:226)
at org.hibernate.jdbc.AbstractBatcher.closeQueryStatement(AbstractBatcher.java:162)
at org.hibernate.loader.Loader.doQuery(Loader.java:714)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224)
at org.hibernate.loader.Loader.loadCollection(Loader.java:1919)
at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:71)
at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:520)
at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60)
at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1627)
at org.hibernate.collection.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:454)
at org.hibernate.engine.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java :827)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:229)
at org.hibernate.loader.Loader.doList(Loader.java:2150)
at org.hibernate.loader.Loader.listIgnoreQueryCache (Loader.java:2029)
at org.hibernate.loader.Loader.list(Loader.java:2024)
at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:369)
at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java :300)
at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:146)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1093)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
at org.springframework.orm.hibernate3.HibernateTemplate$31.doInHibernate(HibernateTemplate.java:853)
at org.springframework.orm.hibernate3.HibernateTemplate.execute(HibernateTemplate.java:366)
at org.springframework.orm.hibernate3.HibernateTemplate.find (HibernateTemplate.java:844)
at org.springframework.orm.hibernate3.HibernateTemplate.find(HibernateTemplate.java:836)
at com.bursatec.bmv.selectividad.persistence.dao.impl.FedCenlacesDaoImpl.findEnlaces(FedCenlacesDaoImpl.java :119)
at com.bursatec.bmv.retransmision.middleware.service.impl.RetransmisorImpl.getEnlaces(RetransmisorImpl.java:229)
at com.bursatec.bmv.retransmision.middleware.service.impl.RetransmisorImpl.getInfoEnlace (RetransmisorImpl.java:242)
at com.bursatec.bmv.retransmision.middleware.service.impl.RetransmisorImpl.efectuarReTx(RetransmisorImpl.java:122)
at com.bursatec.bmv.retransmision.middleware.service.impl.RetransmisorImpl.atenderSolicitud (RetransmisorImpl.java:103)
at com.bursatec.bmv.retransmision.middleware.configura.SubscriptorListener.onMessage(SubscriptorListener.java:22)
at progress.message.jimpl.Session.deliver(Unknown Source)
at progress.message.jimpl.Session.run(Unknown Source)
at progress.message.jimpl.Session$SessionThread.run(Unknown Source)
I wish some one could help me
Thanks a lot. -
Unreported Transaction timeout on commit (Oracle)
I'm expecting an Oracle error upon commit using "deferred constraints" and
executing an INSERT that should result in a constraint violation. I am not
seeing an error but the transaction hangs for 30seconds (JTA timeout
setting) and then continues without an exception. The session bean client
has no indication that the transaction has failed.
I've tried implicit and explicit transations from the client and the session
bean is marked as required.
Weblogic: 8.1 sp1
DB: Oracle 8.1.6
Driver: Oracle Thin XA
How is it possible that Oracle fails upon commit but the JDBC connection
waits for a timeout, and ALSO how is it possible that I'm not seeing a
transaction timeout exception?
(i've changed the JTA timeout setting to verify that this is the timeout
that is occuring and sure enough if i make it 20 seconds it returns after
20, 60, etc...)
M
Settings in Domain_name-JTA and Services-JTA are essentially the same settings. At least this is what I see - my changes to Services-JTA are reflected in Domain_name-JTA.
Edited by: Valery_Cherepanov on 11.08.2012 14:32 -
I'm relatively new to JDeveloper and ADF and have a question regarding queries. I have a recursive master-detail that I'm trying to insert a detail record and programatically commit, re-query and insert a new record. I'm using a java bean on the commit button to set certain fields in addition to those set by the user. Here is the code I'm using:
public String commitDetail() {
BindingContainer bindings = getBindings();
FacesContext fctx = FacesContext.getCurrentInstance();
DCBindingContainer bc = (DCBindingContainer )fctx.getApplication().createValueBinding("#{bindings}").getValue(fctx);
Row masterRw = bc.findIteratorBinding("PartyFinanceMasterAcctViewIterator").getCurrentRow();
Row currentRw = bc.findIteratorBinding("PartyFinanceAccountViewIterator").getCurrentRow();
currentRw.setAttribute("SrcAcctId",masterRw.getAttribute("AcctId"));
currentRw.setAttribute("AcctId",masterRw.getAttribute("AcctId"));
currentRw.setAttribute("TrnsctnDte",masterRw.getAttribute("LockboxDte"));
OperationBinding operationBinding =
bindings.getOperationBinding("Commit");
operationBinding.execute();
if (!operationBinding.getErrors().isEmpty()) {
return null;
OperationBinding operationBindingRfsh =
bindings.getOperationBinding("ExecuteWithParams");
operationBindingRfsh.execute();
if (!operationBinding.getErrors().isEmpty()) {
return null;
OperationBinding operationBinding2 =
bindings.getOperationBinding("CreateInsert");
operationBinding2.execute();
if (!operationBinding.getErrors().isEmpty()) {
return null;
return null;
Any help would be greatly appreciated!
LisaAnother comment, the master row information I'm copying is input by the user.
-
Execution of first request takes lot of time with JDBC OCI
Hi,
We are having an application which connects to Oracle server(10g Enterprise Edition Release 10.2.0.4.0 64bit) using Oracle JDBC OCI driver(10.2.0.1.0 production (10g R2)).
Everything works fine.
But what we observed is randomly the first request to the server vai JDBC driver in a day takes lot of time, varies from 5-15 minutes.
If we execute the request again it executed immediately
What we observed while debugging is preparedStatement.executeQuery() is taking time.
We enabled logging at the JDBC driver layer and a snapshot isgiven below. Between T2CPreparedStatement.doDefineExecuteFetch () and T2CPreparedStatement.execute_for_rows () it takes 5 minutes. Any idea why it takes this much time and reason for it? Oracle driver is not throwing any exceptions
*4-apr-2011 4:00:01* oracle.jdbc.driver.T2CPreparedStatement doDefineExecuteFetch
FINE: T2CPreparedStatement.doDefineExecuteFetch ()
*4-apr-2011 4:05:12* oracle.jdbc.driver.T2CPreparedStatement executeForRows
FINE: T2CPreparedStatement.execute_for_rows () returns: void
Detailed jdbc log is below
-apr-2011 4:00:01 oracle.jdbc.driver.OracleStatement doExecuteWithTimeout
FINE: OracleStatement.doExecuteWithTimeout() needToPrepareDefineBuffer = false
4-apr-2011 4:00:01 oracle.jdbc.driver.PhysicalConnection needLine
FINE: PhysicalConnection.needLine()--no return
4-apr-2011 4:00:01 oracle.jdbc.driver.PhysicalConnection registerHeartbeat
FINE: PhysicalConnection.registerHeartbeat()
4-apr-2011 4:00:01 oracle.jdbc.driver.OracleStatement executeMaybeDescribe
FINE: OracleStatement.execute_maybe_describe() rowPrefetchChanged = false, needToParse = false, needToPrepareDefineBuffer = false, columnsDefinedByUser = false
4-apr-2011 4:00:01 oracle.jdbc.driver.T2CPreparedStatement executeForRows
FINE: T2CPreparedStatement.execute_for_rows (executed_for_describe = false)
4-apr-2011 4:00:01 oracle.jdbc.driver.T2CPreparedStatement doDefineExecuteFetch
FINE: T2CPreparedStatement.doDefineExecuteFetch ()
4-apr-2011 4:05:12 oracle.jdbc.driver.T2CPreparedStatement executeForRows
FINE: T2CPreparedStatement.execute_for_rows () returns: void
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleStatement executeMaybeDescribe
FINE: OracleStatement.execute_maybe_describe():return validRows = 1, needToPrepareDefineBuffer = false
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleStatement doExecuteWithTimeout
FINE: OracleStatement.doExecuteWithTimeout():return validRows = 1, needToPrepareDefineBuffer = false
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl next
FINE: OracleResultSetImpl.next(): closed=false
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl next
FINER: closed=false, statement.currentRow=-1, statement.totalRowsVisited=0, statement.maxRows=0, statement.validRows=1, statement.gotLastBatch=true
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl getString
INFO: OracleResultSetImpl.getString(columnIndex=1)
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl wasNull
INFO: OracleResultSetImpl.wasNull()
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl getString
INFO: OracleResultSetImpl.getString(columnIndex=2)
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl wasNull
INFO: OracleResultSetImpl.wasNull()
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl getString
INFO: OracleResultSetImpl.getString(columnIndex=3)
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl wasNull
INFO: OracleResultSetImpl.wasNull()
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl wasNull
INFO: OracleResultSetImpl.wasNull()
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl getTimestamp
INFO: OracleResultSetImpl.getTimestamp(columnIndex=4)
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl wasNull
INFO: OracleResultSetImpl.wasNull()
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl wasNull
INFO: OracleResultSetImpl.wasNull()
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl next
FINE: OracleResultSetImpl.next(): closed=false
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl next
FINER: closed=false, statement.currentRow=0, statement.totalRowsVisited=1, statement.maxRows=0, statement.validRows=1, statement.gotLastBatch=true
4-apr-2011 4:05:12 oracle.jdbc.driver.PhysicalConnection needLine
FINE: PhysicalConnection.needLine()--no return
4-apr-2011 4:05:12 oracle.jdbc.driver.T2CPreparedStatement closeQuery
FINE: T2CPreparedStatement.closeQuery ()
4-apr-2011 4:05:12 oracle.jdbc.driver.T2CPreparedStatement closeQuery
FINE: T2CPreparedStatement.closeQuery () returns: void
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl close
INFO: OracleResultSetImpl.close()
Regards
SunilHi,
Thanks for the reply
- SQL may vary. Its not the same query which takes time always. The same query executed immediately(using another connection from pool) works perfectly
- If there is a failover or stale connection getting closed or timeout, will JDBC driver thhrows exdeption? I didn't see any exceptions in the driver logs. Is there anyway to identify whether failover or timeout is happening?
Some other points
- The application uses connection pooling. This means that connections are created in the beginning and kept in the pool. And it may be in the pool for 72 hours or , before this issue happens
- Application uses prepared statements and the statements are preapred and kept and re used later. So the query which take s more time might be prepared before 48 hours or so.
- This is not happening every day. Many times the pattern is , it happens after 60-72 hours after application is started.
Sunil
Maybe you are looking for
-
Thinkpad X200 Vista Business 32-bit Wireless network problems
Hey guys! I seem to have a persistent problem with my two Lenovo Thinkpad X200, which I simply can't manage to figure it. I have recently restored the computers to factory settings, which meant downgrading from Windows 8 to Windows Vista Business 32-
-
EJB 3.1 Lite Features Async,Timers ?
Hi I was using glassfish 3.0.1 ,EJB 3.1 timers and async methods were working (in gfish 3.0.1). Now we are moving to glassfish 3.1, And I'm getting following error with EJB 3.1 lite web application. java.lang.RuntimeException: Invalid application. EJ
-
Right click event on TABLE Cell
Hi, I have a TABLE built on my webdynpro screen. Now the requirment is in the first column of the TABLE if the user right clicks on the cell a menu should come which has to be filled with custom menus. Please let me know how that can be acheived. Tha
-
Shortcut to fixed value domain output in ALV
I have a fixed value domain, which has two values...A ='Major Project', B= 'Minor Project'. I wish my alv report to show the long text for fields in this domain. i.e. if a field has a value of A I want the report to show 'Major Project'. Am I going
-
Update locals and limits in the runtime sequence
Hi All! I'm trying to update locals: Engine my_egine = axApplicationMgr.GetEngine(); SequenceFile seq_file = my_egine.GetSequenceFileEx(seq_file_path, TypeConflictHandlerTypes.ConflictHandler_UseGlobalType); Sequence seq = seq_file.GetSequenceByNam