Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 666705, 1 year ago
Transaction timed out after 603 seconds Xid=BEA1-0056ABCB3AD8B145D90D(21001370),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=603,secon ds left=60,activeThread=Thread[ExecuteThread: '47' for queue
via jboss.org by Unknown author, 1 year ago
Transaction timed out after 33 seconds BEA1-02FA63ADA554]
weblogic.transaction.internal.TimedOutException: Transaction timed out after 603 seconds
Xid=BEA1-0056ABCB3AD8B145D90D(21001370),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=603,secon
ds left=60,activeThread=Thread[ExecuteThread: '47' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.k
ernel.Default'],XAServerResourceInfo[JMS_cgJMSStore]=(ServerResourceInfo[JMS_cgJMSStore]=(state=started,assigned=none),xar=JM
S_cgJMSStore,re-Registered = false),SCInfo[integration+m6server]=(state=active),OwnerTransactionManager=ServerTM[ServerCoordi
natorDescriptor=(CoordinatorURL=m6server+172.16.33.35:3001+integration+t3+, XAResources={},NonXAResources={})],CoordinatorURL
=m6server+172.16.33.35:3001+integration+t3+)]	at weblogic.jdbc.jts.Driver.getTransaction(Driver.java:428)	at weblogic.jdbc.jts.Driver.connect(Driver.java:127)	at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)	at com.bea.wli.store.impl.SQLStore$SQLStoreConnection.(SQLStore.java:3137)