Update operation transaction timing out

Hello,
I have a large data structure that needs to be updated atomically (i.e. within a transaction). I am calling the logical service via a web service map, so I presume the transaction starts when the logical service is invoked. It is receiving a transaction timeout on the server, which I suspect is set to 30 seconds at the WebLogic level by our middleware team. (See stack trace below).
The update operation SDO XML is at least 2MB.
1. Is there any way to override this transaction timeout at the service or data space level?
2. Is there any more efficient way to do this update? Sending a big wad of xml is inefficient, and I am not aware of another format supported by ODSI web services. I cannot use mediator API straight from my client to ODSI.
3. If I have to break up my save operation into chunks, is there any way to effectively achieve transactional update via multiple web service calls?
Any advice would be much appreciated.
Thanks,
Jeff
weblogic.xml.query.exceptions.XQuerySystemException: {bea-err}SYS003: Unexpected exception
     at weblogic.xml.query.transaction.TransactionHelper.commit(TransactionHelper.java:96)
     at weblogic.xml.query.transaction.TransactionManager.teardownOnSuccess(TransactionManager.java:178)
     at com.bea.ld.EJBRequestHandler.handleProcessingComplete(EJBRequestHandler.java:1020)
     at com.bea.ld.EJBRequestHandler.handlePusher(EJBRequestHandler.java:979)
     at com.bea.ld.EJBRequestHandler.invokeOperation(EJBRequestHandler.java:323)
     at com.bea.ld.ServerWrapperBean.invoke(ServerWrapperBean.java:153)
     at com.bea.ld.ServerWrapperBean.invokeOperation(ServerWrapperBean.java:80)
     at com.bea.ld.ServerWrapper_s9smk0_ELOImpl.invokeOperation(ServerWrapper_s9smk0_ELOImpl.java:141)
     at com.bea.dsp.ws.RoutingHandler$PriviledgedRunner.run(RoutingHandler.java:96)
     at com.bea.dsp.ws.RoutingHandler.handleResponse(RoutingHandler.java:217)
     at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:287)
     at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:271)
     at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:176)
     at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
     at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
     at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
     at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:285)
     at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:169)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     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:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.transaction.RollbackException: Transaction timed out after 33 seconds
BEA1-460E808DE23C779E385F
     at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1818)
     at weblogic.transaction.internal.TransactionImpl.checkIfCommitPossible(TransactionImpl.java:1708)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:255)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:230)
     at weblogic.xml.query.transaction.TransactionHelper.commit(TransactionHelper.java:94)
     ... 30 more
Caused by: weblogic.transaction.internal.TimedOutException: Transaction timed out after 33 seconds
BEA1-460E808DE23C779E385F
     at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1734)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1607)
     at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1879)
     at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1517)
     at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     ... 2 more

1. Is there any way to override this transaction timeout at the service or data space level?
You can set trans-timeout-seconds in the weblogic-ejb-jar.xml for your dataspace. You'll find it in <dataspaceName>dspejb.jar in <domain>/dsp/dataSpaces/<dataspaceName>request_handlers.ear. I've include a complete weblogic-ejb-jar.xml (at the end of the post) so you can see where to add it. Just copy-paste the <transaction-descriptor>...</>
the request handlers ear is created when the dataspace is deployed the first time and during a full-deploy (i.e. you don't have to go back and edit it after incremental deploys)
2a. Is there any more efficient way to do this update?
If you described it in painful detail, we might be able to think of something. You might find mutators helpful - http://download.oracle.com/docs/cd/E13167_01/aldsp/docs32/dsp32wiki/Mutators%20for%20Updates.html
3. If I have to break up my save operation into chunks, is there any way to effectively achieve transactional update via multiple web service calls?
You could write/host your own webservice on the ODSI server which would call ODSI via the java api. Your ws would expose operations to the following calls from your client
contextId = myWsStartUserTransaction()
while( moreChunks)
myWsUpdate(contextId, chunk)
myWSEndUserTransaction(contextId)
Just a heads-up, WLS has an anti-denial-of-service attack setting that rejects input messages over a certain size. I believe the default is 10MB. You can set it in the WLS console.
- Mike
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN'
'http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>Server</ejb-name>
<stateless-session-descriptor>
<stateless-clustering>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
<stateless-bean-load-algorithm>round-robin</stateless-bean-load-algorithm>


<stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempo
tent>
</stateless-clustering>
</stateless-session-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>com.bea.ld.apps.dataservicesapp.server</jndi-name>
<local-jndi-name>com.bea.ld.apps.dataservicesapp.localserver</local-jndi-name>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>ServerTxRequired</ejb-name>
<stateless-session-descriptor>
<stateless-clustering>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
<stateless-bean-load-algorithm>round-robin</stateless-bean-load-algorithm>


<stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempo
tent>
</stateless-clustering>
</stateless-session-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>com.bea.ld.apps.dataservicesapp.serverTxRequired</jndi-name>
<local-jndi-name>com.bea.ld.apps.dataservicesapp.localserverTxRequired</local-
jndi-name>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>Metadata</ejb-name>
<stateless-session-descriptor>
<stateless-clustering>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
<stateless-bean-load-algorithm>round-robin</stateless-bean-load-algorithm>


<stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idempo
tent>
</stateless-clustering>
</stateless-session-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>com.bea.ld.apps.dataservicesapp.metadata</jndi-name>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>

Similar Messages

Cannot remove stateful session bean when transaction timed out

The transaction timeout is set to 5 minutes. After several operations on the transactional
stateful session bean(implements SessionSynchronization), the transaction timed out
after 5 minutes and I got the IllegalStateException when calling another business
method. After the transaction rolled back, weblogic.ejb20.locks.LockTimedOutException
was thrown when attempting to remove the bean. It seems the lock on the bean was
not released even though the transaction had been rolled back. Does anyone know how
to remove the bean in this kind of situation?
Here is the stacktrace:
####<Jun 11, 2002 2:39:35 PM PDT> <Notice> <EJB> <app1x.zaplet.cc> <server25044server>
<ExecuteThread: '11' for queue: 'default'> <> <23168:7b09681c532dc7e3> <010015> <Error
marking transaction for rollback: java.lang.IllegalStateException: Cannot mark the
transaction for rollback. xid=23168:7b09681c532dc7e3, status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException:
Transaction timed out after 299 seconds
Xid=23168:7b09681c532dc7e3(3203140),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=299,seconds left=60,activeThread=Thread[ExecuteThread: '11' for queue:
'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[server25044+server25044server]=(state=active),properties=({weblogic.jdbc=t3://10.0.100.93:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=server25044server+10.0.100.93:7001+server25044+,
Resources={})],CoordinatorURL=server25044server+10.0.100.93:7001+server25044+)]>
java.lang.IllegalStateException: Cannot mark the transaction for rollback. xid=23168:7b09681c532dc7e3,
status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction
timed out after 299 seconds
Xid=23168:7b09681c532dc7e3(3203140),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=299,seconds left=60,activeThread=Thread[ExecuteThread: '11' for queue:
'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[server25044+server25044server]=(state=active),properties=({weblogic.jdbc=t3://10.0.100.93:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=server25044server+10.0.100.93:7001+server25044+,
Resources={})],CoordinatorURL=server25044server+10.0.100.93:7001+server25044+)]
     at weblogic.transaction.internal.TransactionImpl.throwIllegalStateException(TransactionImpl.java:1486)
     at weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImpl.java:466)
     at weblogic.ejb20.manager.BaseEJBManager.handleSystemException(BaseEJBManager.java:255)
     at weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:215)
     at weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManager.java:371)
     at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:117)
     at weblogic.ejb20.internal.StatefulEJBObject.preInvoke(StatefulEJBObject.java:169)
     at mypackage.MyBean_wbr3eg_EOImpl.addRecipients(MyBean_wbr3eg_EOImpl.java:450)
####<Jun 11, 2002 2:39:37 PM PDT> <Info> <EJB> <app1x.zaplet.cc> <server25044server>
<ExecuteThread: '11' for queue: 'default'> <> <> <010049> <EJB Exception in method:
remove: weblogic.ejb20.locks.LockTimedOutException: The lock request from EJB:AppmailBean
with primary key:21,775,960,933,010,237 timed-out after waiting 0 ms. The transaction
or thread requesting the lock was:Thread[ExecuteThread: '11' for queue: 'default',5,Thread
Group for Queue: 'default'].>
weblogic.ejb20.locks.LockTimedOutException: The lock request from EJB:AppmailBean
with primary key:21,775,960,933,010,237 timed-out after waiting 0 ms. The transaction
or thread requesting the lock was:Thread[ExecuteThread: '11' for queue: 'default',5,Thread
Group for Queue: 'default'].
     at weblogic.ejb20.locks.ExclusiveLockManager$LockBucket.lock(ExclusiveLockManager.java:448)
     at weblogic.ejb20.locks.ExclusiveLockManager.lock(ExclusiveLockManager.java:258)
     at weblogic.ejb20.manager.StatefulSessionManager.acquireLock(StatefulSessionManager.java:226)
     at weblogic.ejb20.manager.StatefulSessionManager.acquireLock(StatefulSessionManager.java:216)
     at weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManager.java:310)
     at weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.java:754)
     at weblogic.ejb20.internal.StatefulEJBObject.remove(StatefulEJBObject.java:86)
     at mypackage.MyBean_wbr3eg_EOImpl.remove(MyBean_wbr3eg_EOImpl.java:7308)

If a stateful session throws a RuntimeException (your rollback) the container destroys the instance of the bean and all
associated state information is lost, as required by the EJB specification.
If you want to maintain client state it is generally best to use HttpSession objects (if you have a web application)
for short-lived, client-specific data and JPA entities or other database backed storage for long-lived data.

TMG 2010 report problem Operation has timed out

Hello.
I stuck and i'm really need assistance
We has a TMG 2010 RTM version and i decide to update it to latest rollup and SP (dumb head)
So at now we have TMG 2010 SP2 rollup 4.
Before i update TMG reports work fine but at now reports not working at all.
When i try execute a report ( or shedule daily or weekly report) i have same issue
Error 31289:
The report "Daily" could not be generated. Report Server error information: The report Daily could not be generated. Report Server error information: The operation has timed out.
The error occurred on object 'Reports' of class 'Reports Configuration' in the scope of array 'TMG`
I read all guidliness( include this http://www.isaserver.org/tutorials/Microsoft-Forefront-TMG-How-to-use-SQL-Server-2008-Express-Reporting-Services.html) and not find something useful.
Settings correct, and i not changed any settings.
And at now my ideas end i ask your help.

That would be expected as the RAT key does not exist by default on a TMG system. You will need to create it and the subkeys referenced along with the values.
Create as described in the article.
Hth, Anders Janson Enfo Zipper

The transaction is no longer active - Transaction timed out after 30 second

We have an intermittent error here, and I'm a rookie. The error results in a 500 being sent to the customer every 10th-20th POST and only occurs under heavy load. The heavy loading is over the for the day, but it'll be back.
My first suspicion was the app code doing transaction work and having database performance problems. But the app is non-transactional and the database is fine. The server farm nodes (4) are all experiencing the problems at equal rates, and the other apps on the farm are fine, so it appears to be app-specific rather than rooted in server state or database state.
I looked at the stack a little more closely and it appears to be some kind of internal persistence issue, but a completely foreign one to me. We have no Persistent Stores configured, so I don't know where to even start on this puppy.
EJB Exception occurred during invocation from home: weblogic.ejb.container.internal.StatelessEJBLocalHomeImpl@d1e1f4 threw exception: <1.0.0 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
<1.0.0 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:3784)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:97)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:83)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:59)
at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.handleCheckedException(SelectResultObjectProvider.java:155)
at org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:40)
at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1219)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:987)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:839)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:770)
at kodo.kernel.KodoQuery.execute(KodoQuery.java:47)
at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:525)
at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:229)
at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:269)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactionsExcludingApplication(ApproveApplicationHelper.java:167)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactions(ApproveApplicationHelper.java:129)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.stageAction(ApproveApplicationHelper.java:74)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean.performAction(ApproveApplicationSessionBean.java:348)
at sun.reflect.GeneratedMethodAccessor2150.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:281)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:187)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:154)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at weblogic.ejb.container.injection.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:68)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
at $Proxy365.performAction(Unknown Source)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.performAction(ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.java:148)
at com.company.buapp.si.ApplicationWS.performAction(ApplicationWS.java:114)
at sun.reflect.GeneratedMethodAccessor2149.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:50)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:42)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:247)
at com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:97)
at weblogic.wsee.jaxws.MonitoringPipe.process(MonitoringPipe.java:98)
at com.sun.xml.ws.protocol.soap.ServerMUPipe.process(ServerMUPipe.java:62)
at com.sun.xml.ws.server.WSEndpointImpl$1.process(WSEndpointImpl.java:139)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:153)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:235)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:97)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:36)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:218)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 30 seconds
BEA1-32AE928C966AC66F424D]'. No further JDBC access is allowed within this transaction.
at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:178)
at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:188)
at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:57)
at weblogic.jdbc.wrapper.ResultSet_oracle_jdbc_driver_OracleResultSetImpl.next(Unknown Source)
at org.apache.openjpa.lib.jdbc.DelegatingResultSet.next(DelegatingResultSet.java:106)
at org.apache.openjpa.jdbc.sql.ResultSetResult.nextInternal(ResultSetResult.java:210)
at org.apache.openjpa.jdbc.sql.SelectImpl$SelectResult.nextInternal(SelectImpl.java:2209)
at org.apache.openjpa.jdbc.sql.AbstractResult.next(AbstractResult.java:168)
at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.next(SelectResultObjectProvider.java:99)
at org.apache.openjpa.lib.rop.EagerResultList.<init>(EagerResultList.java:35)
at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1219)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:987)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:839)
at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:770)
at kodo.kernel.KodoQuery.execute(KodoQuery.java:47)
at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:525)
at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:229)
at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:269)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactionsExcludingApplication(ApproveApplicationHelper.java:167)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactions(ApproveApplicationHelper.java:129)
at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.stageAction(ApproveApplicationHelper.java:74)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean.performAction(ApproveApplicationSessionBean.java:348)
at sun.reflect.GeneratedMethodAccessor2150.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:281)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:187)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:154)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at weblogic.ejb.container.injection.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:68)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
at $Proxy365.performAction(Unknown Source)
at com.company.buapp.buslogic.session.ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.performAction(ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.java:148)
at com.company.buapp.si.ApplicationWS.performAction(ApplicationWS.java:114)
at sun.reflect.GeneratedMethodAccessor2149.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:50)
at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:42)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:247)
at com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:97)
at weblogic.wsee.jaxws.MonitoringPipe.process(MonitoringPipe.java:98)
at com.sun.xml.ws.protocol.soap.ServerMUPipe.process(ServerMUPipe.java:62)
at com.sun.xml.ws.server.WSEndpointImpl$1.process(WSEndpointImpl.java:139)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:153)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:235)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:97)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:36)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:218)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3395)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

This was actually my first conclusion as well. But when I went to the Data Source for this connection, I found it's a non-transactional driver. That's what made me go back and give the trace a second look. I don't see any references to the Data Source in question. It's OpenJPA stuff and Session persistence stuff.Non-XA drivers can still participate in an XA transaction via a variety of JDBC data source options - for example, labeled "1PC" and "LLR" on the console. (If you want to understand the particulars search for "JTS" or "LLR" in the JDBC edocs).
You seem to be suggesting maybe the setting can be made in a config doc, possibly of the app itself, right? Right. EJBs have a transaction-timeout attribute.
As opposed to setting it in the console. WebLogic has a domain wide default transaction-timeout setting that can be set on the console, but I tend not to recommend using it. In addition, there's something called a "deployment plan" which can be used to override some of the common EJB attributes via configuration, but I'm not personally familiar with its usage.
But isn't the setting vapor if we're using a nonXA driver?No.
I wonder if this thing couldn't be telling me it's waiting on the persistence subsystem to come available to store simple session data? Sometimes the problem is that there are periodic app requests that are more complex/larger than others. Sometimes the system is simply overloaded, and takes 30 seconds to honor a request that might normally take 10 seconds.
That other app is all about persistence. What if app2 is sucking some persistence subsystem dry and app 1 is waiting just to store session data? Could be.
If the nonXA thing really does kill the quick timeout workaround, how could I health-check the persistence subsystem?Don't know. At a wild guess I'd check for CPU's at 100% on all involved serves, and examine database stats.

The operation has timed out

Hello Forum,
I was running a report that was built on report builder at some point an error message of the operation has timed out will come up.
I have set the time out to 0 values and more than 600 seconds too.
On SQL the report ran within 6 minute.
Will be glad for quick response.
Thank you.
Disu Ridwan

Hi Disu,
I assumed that you open the report builder from the report manager or you have connectted to the report server.
As you have mentioned that set the timeout value of the dataset didn't work. Please reference to the similer thread below to set the other time out in the configuration file and so on:
Report Builder 2.0 / 3.0 errors out with 'The operation
has timed out' when previewing a report saved in Report Server takes more than 10 minutes
Steps to Resolve SSRS Timeout Issues
"The operation has timed out" when rendering a report
If you problem still exists, please feel free to ask.
Regards
Vicky Liu
Vicky Liu
TechNet Community Support

Error message... operation has timed out

My new ipod for my daughter will not show up in itunes. It says i need to download the latest version (10.5) of itunes. Every time I attempt to download itunes 10.5, I get the error message "the operation has timed out" itunes could not be downloaded. How do I download the latest version? I want to put songs on my daughters new ipod. Thanks

Temporarily turn off any virus protection and firewall.

Collab CopyProjectMetaData - the operation has timed out

For the life of me, I can't get the CopyProjectMetaData to run w/o timing out. It'll work about 1 in 10 trys if that. I'm using CopyProjectContent on the same two projects successfully everytime. But CopyProjectMetaData is basically useless. Anyone?

Hi Disu,
I assumed that you open the report builder from the report manager or you have connectted to the report server.
As you have mentioned that set the timeout value of the dataset didn't work. Please reference to the similer thread below to set the other time out in the configuration file and so on:
Report Builder 2.0 / 3.0 errors out with 'The operation
has timed out' when previewing a report saved in Report Server takes more than 10 minutes
Steps to Resolve SSRS Timeout Issues
"The operation has timed out" when rendering a report
If you problem still exists, please feel free to ask.
Regards
Vicky Liu
Vicky Liu
TechNet Community Support

Question about EWS - The operation has timed out

hi everyone,
I'm developing a solution which uses public folder database in Exchange Server to store tasks:
- We use 1 account to access to public folder database by using EWS.
- Currently, this public folder database contains 60000 tasks and they are being accessed by 700 users, they always have the following exception:
04/23/2015 09:41:15: - The request failed. The operation has timed out
Message :The request failed. The operation has timed out
Source :Microsoft.Exchange.WebServices
Stack Trace : at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
at Microsoft.Exchange.WebServices.Data.ExchangeService.FindItems[TItem](IEnumerable`1 parentFolderIds, SearchFilter searchFilter, String queryString, ViewBase view, Grouping groupBy, ServiceErrorHandling errorHandlingMode)
at Microsoft.Exchange.WebServices.Data.ExchangeService.FindItems(FolderId parentFolderId, SearchFilter searchFilter, ViewBase view, Grouping groupBy)
Please help.
Thanks a lot.
Phuc

Thanks Glen for your reply.
Here is a code block which retrieve the number of task of some groups
foreach (var bu in request.BusinessUnits)
SearchFilter businessUnitFilter = new SearchFilter.IsEqualTo(BusinessUnitAliasProp, bu);//, ContainmentMode.FullString, ComparisonMode.IgnoreCase);
SearchFilter[] filters = new SearchFilter[] { actualOwnerFilter, statusFilter, businessUnitFilter };
var filterCollection = new SearchFilter.SearchFilterCollection(LogicalOperator.And, filters);
GroupedFindItemsResults<Item> taskResults = this.exchangeService.FindItems(_publicFolderId, filterCollection, itemView, groupByApplication);
if (taskResults != null && taskResults.ItemGroups != null)
foreach (var groupItem in taskResults.ItemGroups)
if (!dict.ContainsKey(groupItem.GroupIndex))
dict.Add(groupItem.GroupIndex, new Dictionary<string, int>());
if (!dict[groupItem.GroupIndex].ContainsKey(bu))
dict[groupItem.GroupIndex].Add(bu, groupItem.Items.Count);
Please let me know if it's too complex and might affect to the performance of Exchange Server

Transaction timed out with oracle 9i

Hi,
I am working with weblogic6.1.
Sometimes (very seldom) I have a problem which I don't undserstand.
The transaction stops and and after some time I get TimedOutException.
This time it happend in the findByPrimaryKey of a CMP Entity bean.
I have this problem only with Oracle 9i. with oracle8i everything works
fine.
I'm using oracle thin driver (I put oracle12.zip at the begin of weblogic
classpath)
Is this problem of oracle?
Does WLS 6.1 support Oracle9i?
Thanks for any hints
Szymon
stack trace:
javax.ejb.FinderException: Problem in findByPrimaryKey while preparing or
execut
ing statement: 'weblogic.jdbc.rmi.SerialPreparedStatement@197155':
java.sql.SQLException: The transaction is no longer active (status = Marked
roll
back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction
timed
out after 561 seconds
Xid=21550:aea95ccd7f28edb9(4655671),Status=Active,numRepliesOwedMe=0,numRepl
iesO
wedOthers=0,seconds since begin=561,seconds
left=30,activeThread=Thread[ExecuteT
hread: '14' for queue: 'default',5,Thread Group for Queue:
'default'],ServerReso
urceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[
mydo
main+myserver]=(state=active),properties=({weblogic.jdbc=t3://172.16.0.28:70
01})
,OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorUR
L=my
server+172.16.0.28:7001+mydomain+,
Resources={})],CoordinatorURL=myserver+172.16
.0.28:7001+mydomain+)]). No further JDBC access is allowed within this
transact
ion.
java.sql.SQLException: The transaction is no longer active (status = Marked
roll
back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction
timed
out after 561 seconds
Xid=21550:aea95ccd7f28edb9(4655671),Status=Active,numRepliesOwedMe=0,numRepl
iesO
wedOthers=0,seconds since begin=561,seconds
left=30,activeThread=Thread[ExecuteT
hread: '14' for queue: 'default',5,Thread Group for Queue:
'default'],ServerReso
urceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[
mydo
main+myserver]=(state=active),properties=({weblogic.jdbc=t3://172.16.0.28:70
01})
,OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorUR
L=my
server+172.16.0.28:7001+mydomain+,
Resources={})],CoordinatorURL=myserver+172.16
.0.28:7001+mydomain+)]). No further JDBC access is allowed within this
transact
ion.
at
weblogic.jdbc.jts.Connection.checkIfRolledBack(Connection.java:498)
at weblogic.jdbc.jts.Statement.setInt(Statement.java:606)
at
weblogic.jdbc.rmi.internal.PreparedStatementImpl.setInt(PreparedState
mentImpl.java:104)
at
weblogic.jdbc.rmi.SerialPreparedStatement.setInt(SerialPreparedStatem
ent.java:137)
at
com.verdisoft.datasource.ejb.contact.Person_vjvtzf__WebLogic_CMP_RDBM
S.ejbFindByPrimaryKey(Person_vjvtzf__WebLogic_CMP_RDBMS.java:1531)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.findByPrimaryKey(RDB
MSPersistenceManager.java:171)
at
weblogic.ejb20.manager.BaseEntityManager.findByPrimaryKey(BaseEntityM
anager.java:435)
at
weblogic.ejb20.manager.BaseEntityManager.localFindByPrimaryKey(BaseEn
tityManager.java:389)
at
weblogic.ejb20.internal.EntityEJBLocalHome.findByPrimaryKey(EntityEJB
LocalHome.java:266)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
findByPrimaryKey(PersonBean_vjvtzf_LocalHomeImpl.java:144)
at
com.verdisoft.datasource.ejb.contact.PersonBean.ejbHomeGetByKey(Perso
nBean.java:504)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
getByKey(PersonBean_vjvtzf_LocalHomeImpl.java:297)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.getBeanAdapter(EJBAdapter
Bean.java:872)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItemInternal(EJBAda
pterBean.java:834)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItem(EJBAdapterBean
.java:808)
at
com.verdisoft.datasource.ejb.EJBAdapterBean_s83q9a_EOImpl.updateItem(
EJBAdapterBean_s83q9a_EOImpl.java:146)
at
com.verdisoft.datasource.DataAdapterManagerBean.updateItem(DataAdapte
rManagerBean.java:144)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl.updateI
tem(DataAdapterManagerBean_plajw8_EOImpl.java:614)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl_WLSkel.
invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:282)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:97)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:231)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:144)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
at
com.verdisoft.datasource.ejb.contact.Person_vjvtzf__WebLogic_CMP_RDBM
S.ejbFindByPrimaryKey(Person_vjvtzf__WebLogic_CMP_RDBMS.java:1715)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.findByPrimaryKey(RDB
MSPersistenceManager.java:171)
at
weblogic.ejb20.manager.BaseEntityManager.findByPrimaryKey(BaseEntityM
anager.java:435)
at
weblogic.ejb20.manager.BaseEntityManager.localFindByPrimaryKey(BaseEn
tityManager.java:389)
at
weblogic.ejb20.internal.EntityEJBLocalHome.findByPrimaryKey(EntityEJB
LocalHome.java:266)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
findByPrimaryKey(PersonBean_vjvtzf_LocalHomeImpl.java:144)
at
com.verdisoft.datasource.ejb.contact.PersonBean.ejbHomeGetByKey(Perso
nBean.java:504)
at
com.verdisoft.datasource.ejb.contact.PersonBean_vjvtzf_LocalHomeImpl.
getByKey(PersonBean_vjvtzf_LocalHomeImpl.java:297)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.getBeanAdapter(EJBAdapter
Bean.java:872)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItemInternal(EJBAda
pterBean.java:834)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItem(EJBAdapterBean
.java:808)
at
com.verdisoft.datasource.ejb.EJBAdapterBean_s83q9a_EOImpl.updateItem(
EJBAdapterBean_s83q9a_EOImpl.java:146)
at
com.verdisoft.datasource.DataAdapterManagerBean.updateItem(DataAdapte
rManagerBean.java:144)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl.updateI
tem(DataAdapterManagerBean_plajw8_EOImpl.java:614)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl_WLSkel.
invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:282)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:97)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:231)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:144)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
com.verdisoft.datasource.exception.DataNotFoundException: Object not found:
data
source://private_addressbook/ejbcontact/john1025100151518/12770
at
com.verdisoft.datasource.ejb.EJBAdapterBean.getBeanAdapter(EJBAdapter
Bean.java:876)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItemInternal(EJBAda
pterBean.java:834)
at
com.verdisoft.datasource.ejb.EJBAdapterBean.updateItem(EJBAdapterBean
.java:808)
at
com.verdisoft.datasource.ejb.EJBAdapterBean_s83q9a_EOImpl.updateItem(
EJBAdapterBean_s83q9a_EOImpl.java:146)
at
com.verdisoft.datasource.DataAdapterManagerBean.updateItem(DataAdapte
rManagerBean.java:144)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl.updateI
tem(DataAdapterManagerBean_plajw8_EOImpl.java:614)
at
com.verdisoft.datasource.DataAdapterManagerBean_plajw8_EOImpl_WLSkel.
invoke(Unknown Source)

Irene Ho wrote:
Dear all,
When the java application program tries to insert the data (around 300
records). Sometimes, the error occurs as "EJB Exception:
weblogic.transaction.internal.TimedOutException: Transaction timed out after
95 seconds".
When the error occurred, only one java application was running. Furthermore,
I set the JTA-->Timeout Seconds to 30 in the thr the Weblogic console. The
configuration of the server is WebLogic 7.0 with SP2 and Oracle 8.1.7.
Anyone know what happen and how to resolve the problem? The error is due to
the entity bean, Weblogic or Oracle?
Thanks a lot.
IreneOr configuration. You can set your timeout to a different value. It is likely
to be an oracle problem. We don't do anything unnecessary to delay your application
code. You may be able to check the jdbc log or jta log to see when the tx starts and
how long it takes to progress. If you note a delay, you could take a server
thread dump to see what weblogic is doing. Typically it will be waiting for
Oracle to respond from a jdbc call.
Joe

Transaction timed out

When the java program tries to insert the data (around 300 records), the error occurs as "EJB Exception: weblogic.transaction.internal.TimedOutException: Transaction timed out after 95 seconds"
Anyone know what happen and how to resolve the problem?
Furthermore, any method to record such an error into the Oracle log?
Thanks a lot.

Judging from the exception, it would appear that this is something that WebLogic is taking upon itself to throw. I'm assuming that somewhere in your WebLogic configuration, you have configured a timeout of 95 seconds. If that's the case, you would need to modify your WebLogic configuration to increase that timeout.
Oracle has no limit on the amount of time a transaction can be open, so this error has to be caused by the application server. As such, I don't see any way to get this sort of error into any of the Oracle logs (I assume we're talking about trace files and alert logs on the Oracle server here). If your code caught this error, you could insert the error into an error log table in the Oracle database.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Transaction timed out after 29seconds

          hi,
          I am using 2pc with XA, for MQ and Sybase
          I am getting following exception.
          [Reason = weblogic.transaction.internal.TimedOutException: Transaction timed out
          after 29seconds
          can somebody help me on this ?
          TIA
          Chidambar


default value of transaction timeout is 30 secs.
          Your tx may be running more than the default tx timeout.
          Either increase your tx timeout or re-consider your
          design.
          Kumar
          chidambar wrote:
          > hi,
          > I am using 2pc with XA, for MQ and Sybase
          > I am getting following exception.
          > ................................................................
          >
          > [Reason = weblogic.transaction.internal.TimedOutException: Transaction timed out
          > after 29seconds
          >
          > ................................................................
          > can somebody help me on this ?
          > TIA
          > Chidambar

Transaction timing out

I have a problem with transaction timing out and I know how to increase the time out interval but I would just like to learn as to what exactly is going on and how I can fix the problem without increasing the timeout.
class RequestProcessor {
public void do() {
// very long process
doSomeWhereLongProcess()
// retrieve another session bean
persistence = (IPersistence) ctx.lookup( IPersistence.JNDI_NAME );
persistence.insert()
doSomeProcess();
public class PersistenceFacade implements IPersistence {
     @PersistenceContext
     private EntityManager em;
// calls an entityManager to retrieve
public void retrieve()
RequestProcessor is a session bean that is being called remotely. In ejb-jar.xml transaction type is set to Bean.
It calls another session bean called PeristenceFacade that contains entity manager to insert entity beans. The transaction type in PersistenceFace
is set to Container.
While still executing a doSomeWhereLongProcess I get notification in log that transaction timed out and when it tries to called PersistenceFacade
I get an exception. Why would it start a transaction even before I looked up a PersistenceFacade?
I tried setting transaction type to Bean in PersistenceFacade but it is complaining that EntityManager must have a transaction.
What is the proper way of handling this type of scenario? Is is simply increasing the timeout or can I handle this differently?
Thanks

Yes, it's perfectly legal to define a bean with bean-managed transaction management that doesn't actually start a transaction. In that case, the question is where the transaction is getting started. Even for beans with container-managed transactions, @PostContruct for a session bean is never a transactional method, so it seems odd that a new transaction would be started there unless some piece of application code is starting it.
You might want to post to a JBoss forum to get more info. You can try running your application on the Java EE SDK or using the verifier in the Java EE SDK to see if it detects any issues.
--ken

How can I restore my sons itouch to original settings without doing the restore through iTunes? He can't remember his passcode and when I try to restore through iTunes it never completes the update/restore without timing out?!?!

HOw can I restore my sons itouch to original settings without going through iTunes restore? When I plug into iTunes it will never complete the update/restore without timing out? He can't remember his password. I can't get my iTunes to update to the newest level either without timing out. Please help!

The thread title differs from the original post, sorry for the confusion. I read password instead of passcode.
The only way past a passcode lock is by entering the passcode. Refer to HT1212 iOS: Wrong passcode results in red disabled screen:
If you cannot remember the passcode, you will need to restore your device using the computer with which you last synced it. This allows you to reset your passcode and resync the data from the device (or restore from a backup).
If you restore on a different computer that was never synced with the device, you will be able to unlock the device for use and remove the passcode, but your data will not be present.
As for timing out during the restore...
If there isn't any antivirus or firewalls in the way, I would try restoring from a different user account or even a different computer. If still unable to restore without timing out, I would try a different network.

Cannot send mails to mail server. (The operation has timed out.)

I have configured database mail in sql server 2008 r2 on my local machine.
While testing I have observed that some of mails are not getting triggered.
Log file shows following message-
The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 7 (2013-04-30T10:23:57).
Exception Message: Cannot send mails to mail server. (The operation has timed out.)
I have wriitten on SP for snding mails which sends 94 mail to different ail
address out of which only 35 are getting delivered.
Plz Assist me.

Hi Prashant Parit,
Please apply the latest SQL Server 2008 R2 Service Pack. And try to stop and restart SQL Server Agent.
See similar thread:
http://social.msdn.microsoft.com/Forums/en-US/sqltools/thread/6d3cd4ca-0a4e-4c84-bf1e-b8565c963c38.
Thanks.
Maggie Luo
TechNet Community Support

The operation has timed out default value too low - c# windows application

Hello,
I get the message that the operation has timed out when certain operations take too long, which would be any on our development/test server.
I either need to make an asychronous call which I will investigate or to find the code that sets this value to ten minutes.
Anybody know how to reset the value to ten minutes?
Thanks,
Stephanie

The timeout is occurring on the client so it not a particular error that's being returned by the server.
The default timeout with the EWS Managed API is 90 seconds and is set on the ExchangeService Object. You can set this to a higher value eg to set it to 5 minutes
server.timeout = 300000;
Why it fails ? if its overnight then Backups can be the cause eg if they are snapshotting the server or some other backup mechanism could mean the server is very busy for a time. Or any other number of specific environmental factors. This is really
a job for your Network admin to determine with server and network monitoring. I would suggest you check the EWS.Log on the Exchange server to see what happened at that time.
What you should do at a code level is handle the exception, I would suggest wait for 60 seconds after the exception (this will cater for most throttling issues) and then try the same request again. If it fails again after a pause then
you generally have a larger problem.
Cheers
Glen

Update operation transaction timing out

Similar Messages

Maybe you are looking for