Weblogic.transaction.TimedOutException

I get error message from Weblogic 10.3
weblogic.transaction.TimedOutException: Transaction timed out after 31 seconds
Please, tell me where can I increase this time out interval on server?
Thanks.

Hi Creed,
You can solve you issue by increase the transaction timeout value from console as show below
Login to AdminConsole
Environments --> <DomainName> (ClickHere) ---> Configuration (Tab) ---> JTA (SubTab) ----> in this page try to set the Transcation timeout
By default the value is 30 Seconds at the Domain level, however your transaction might need more time, hence increasing this value would surely solve your issue.
Regards,
Ravish Mody
http://middlewaremagic.com/weblogic/
Come, Join Us and Experience The Magic…

Similar Messages

Weblogic.transaction.internal.TimedOutException while JMS adapter De queuing

Hi ,
I am getting the weblogic.transaction.internal.TimedOutException in SOA logs, when i track the instance using ecid. I am unable to find the flow in EM.
EM shows that instance as complete and I can able to see only the JMS adapter in flow trace.
Increasing the timeout is not a good option, I hope. It’s already set to 10800.
Error msg:
Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 10798
I am not sure y the De queuing take such a long time?? Any other thought guys??
Regards,
Ram.

Could you check the size of the JMS message that is getting polled.
When the transaction is getting rolled back, is the JMS message getting discarded or present in JMS Queue

CMP Bean - weblogic.transaction.internal.TimedOutException

Hi,
I have two CMP beans. Bean1 is stateless bean and Bean2 is stateful. I am
using a method of Bean2 from Bean1 and later on call Bean1.remove(). Now, I
am getting the following error in my application. I would appreciate any
help.
Thanks,
SamK
weblogic.transaction.internal.TimedOutException: Transaction timed out
after 62 seconds
2240:505a02f68bbeb855
java.rmi.RemoteException: Transaction Rolledback.; nested exception is:
weblogic.transaction.internal.TimedOutException: Transaction timed out
after 62 seconds
2240:505a02f68bbeb855
weblogic.transaction.internal.TimedOutException: Transaction timed out after
62 seconds
2240:505a02f68bbeb855
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
Impl.java:1214)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
ansactions(ServerTransactionManagerImpl.java:888)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
erImpl.java:1695)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
sactionManagerImpl.java:813)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1661)
at java.lang.Thread.run(Thread.java:479)

Do you really mean to say 'CMP beans'? Usually the terms stateless and
stateful are applied to
session beans.
Seth
"Sameer Karmarkar" <[email protected]> wrote in message
news:[email protected]..
Hi,
I have two CMP beans. Bean1 is stateless bean and Bean2 is stateful. I am
using a method of Bean2 from Bean1 and later on call Bean1.remove(). Now,I
am getting the following error in my application. I would appreciate any
help.
Thanks,
SamK
weblogic.transaction.internal.TimedOutException: Transaction timed out
after 62 seconds
2240:505a02f68bbeb855
java.rmi.RemoteException: Transaction Rolledback.; nested exception is:
weblogic.transaction.internal.TimedOutException: Transaction timed out
after 62 seconds
2240:505a02f68bbeb855
weblogic.transaction.internal.TimedOutException: Transaction timed outafter
>
62 seconds
2240:505a02f68bbeb855
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
>
Impl.java:1214)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
>
ansactions(ServerTransactionManagerImpl.java:888)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
>
erImpl.java:1695)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
>
sactionManagerImpl.java:813)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
>
rImpl.java:1661)
at java.lang.Thread.run(Thread.java:479)

Weblogic.transaction.internal.TimedOutException

Weblogic transactions are defaulted to time out after 300 seconds and when we make multiple calls to the process(JPD), the response time of the call pushes us over the 300 seconds. I get TimeedOutException
          Is there Any option to solve this issue.
          Thanks in Advance
          Rabik

look at the file:
...installdir...\odsi_10.3\deployment\weblogic-ejb-jar.xml
Make a copy of the original for safety's sake, and directly following the </stateless-session-descriptor> for the Server ejb, explicitly add the element
<transaction-descriptor>
     <trans-timeout-seconds>600</trans-timeout-seconds>
</transaction-descriptor>
Be aware that this change will affect all of your applications built using this particular ODSI installation.
Now, explicitly delete your dataspace from the server and then redeploy it. It should now have the new timeout. If you need a shorter timeout, you can use the fn-bea:timeout() function in your function, or specify a timeout in RequestConfig when making the call.
- Mike

Doubts on weblogic transaction

          Hi,
          I have done a testing on transaction, and found something strange:
          when the transcation timeout, I found there were two thread running and not released:
          1. the thread running the transaction(even the transaction was timeout, this thread
          was still running, why?);
          2. the thread which was running:weblogic.transaction.internal.TransactionImpl$1(why
          consume another thread in "default" queue to run the job,and for what? )
          3. what happened to that DB connection, will it be returned to pool again?Can
          it be used again?
          Thanks


          Hi, Joseph:
          here is the thread dump:
          "ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0xf2cee20 nid=0x6f0
          waiting for monitor entry [0x1054f000..0x1054fdc0]
               at oracle.jdbc.driver.OracleConnection.rollback(OracleConnection.java:1364)
               at weblogic.jdbc.jts.Connection.internalRollback(Connection.java:806)
               at weblogic.jdbc.jts.Connection.rollback(Connection.java:516)
               at weblogic.transaction.internal.ServerResourceInfo.rollback(ServerResourceInfo.java:1416)
               at weblogic.transaction.internal.ServerResourceInfo.rollback(ServerResourceInfo.java:671)
               at weblogic.transaction.internal.ServerSCInfo.startRollback(ServerSCInfo.java:394)
               at weblogic.transaction.internal.ServerTransactionImpl.localRollback(ServerTransactionImpl.java:1538)
               at weblogic.transaction.internal.ServerTransactionImpl.globalRollback(ServerTransactionImpl.java:2164)
               at weblogic.transaction.internal.TransactionImpl$1.execute(TransactionImpl.java:1673)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
          "ExecuteThread: '11' for queue: 'default'" daemon prio=5 tid=0xf1708a0 nid=0x6f8
          runnable [0x1050f000..0x1050fdc0]
               at oracle.jdbc.oci8.OCIDBAccess.do_execute(Native Method)
               at oracle.jdbc.oci8.OCIDBAccess.executeFetch(OCIDBAccess.java:1732)
               at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2053)
               at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1940)
               at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2709)
               at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
               at weblogic.jdbc.jts.Statement.executeUpdate(Statement.java:509)
               at jsp_servlet.__test_jdbc._jspService(__test_jdbc.java:111)
               at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
               at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
               at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
               at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
          Thanks&Regards
          >
          >
          >lumin wrote:
          >
          >> After the transaction timeout, I monitor through weblogic console and
          >get the thread
          >> message:
          >>
          >> thead 8 still running, Http Request: /life/test_jdbc.jsp {weblogic.transaction.internal.JTATransactionImpl:
          >> name=null, xid=2:e33999517f28edb9, status=Rolling Back. [Reason=weblogic.transaction.internal.TimedOutException:
          >> Transaction timed out after 30 seconds Xid=2:e33999517f28edb9(8304246),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
          >> since begin=30,seconds left=30,activeThread=Thread[ExecuteThread: '8'
          >for queue:
          >> 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none,xar=weblogic.jdbc.jts.Connection@7d1491),SCInfo[mydomain+myserver]=(state=active),properties=({weblogic.jdbc=t3://172.16.6.2:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myserver+172.16.6.2:7001+mydomain+t3+,
          >> Resources={})],CoordinatorURL=myserver+172.16.6.2:7001+mydomain+t3+)],
          >userProperties={weblogic.jdbc=t3://172.16.6.2:7001},
          >> secondsActive=103, servers=myserver, resourceNamesAndStatus=weblogic.jdbc.jts.Connection/started}
          >>
          >>
          >> thread 7 is also running: weblogic.transaction.internal.TransactionImpl$1@1f1321
          >>
          >>
          >> When I rollback the delete operation, thread 7 disappear first, after
          >a while,
          >> thread 8 also disapper.
          >> But if I let it be, thread 7 and thread 8 will not stop running.
          >
          >Ok. Oracle's driver is unable to interrupt certain DBMS activity, even
          >if a
          >rollback is called on the connection. However, please duplicate the hanging,
          >and please show me the full stack trace of the two hanging threads.
          >thanks,
          >Joe
          >
          >>
          >>
          >> Thanks&Regards
          >> >
          >> >
          >> >lumin wrote:
          >> >
          >> >> Hi, Joseph:
          >> >>
          >> >> Thanks for your revert.Here is the platform information for testing:
          >> >>
          >> >> operating system:Windows2000 professional
          >> >> app server: weblogic 7.0 sp4
          >> >> database client: oracle 9.2.0.1
          >> >> DB driver: Oracle OCI driver
          >> >> what am I doing: delete a record from command line and didn't commit/rollback;
          >> >> then running a JSP program which trying to update the deleted record.
          >> >
          >> >Ok, and what happens when you comit or rollback the SQL-PLUS session?
          >> >Joe
          >> >
          >> >>
          >> >>
          >> >> Thanks&Regards.
          >> >>
          >> >> >
          >> >> >lumin wrote:
          >> >> >
          >> >> >> Hi,
          >> >> >>
          >> >> >> I have done a testing on transaction, and found something strange:
          >> >> >>
          >> >> >> when the transcation timeout, I found there were two thread running
          >> >> >and not released:
          >> >> >>
          >> >> >> 1. the thread running the transaction(even the transaction was
          >timeout,
          >> >> >this thread
          >> >> >> was still running, why?);
          >> >> >> 2. the thread which was running:weblogic.transaction.internal.TransactionImpl$1(why
          >> >> >> consume another thread in "default" queue to run the job,and
          >for
          >> >what?
          >> >> >)
          >> >> >> 3. what happened to that DB connection, will it be returned to
          >pool
          >> >> >again?Can
          >> >> >> it be used again?
          >> >> >>
          >> >> >> Thanks
          >> >> >
          >> >> >Hi. Depending on what DBMS and what JDBC driver you are using,
          >and
          >> >what
          >> >> >the JDBC Connection is doing at the time, it may not return from
          >it's
          >> >> >activity
          >> >> >even though we've sent a rollback() to the connection. What version
          >> >of
          >> >> >the server
          >> >> >are you using?
          >> >> >Joe
          >> >> >
          >> >> >
          >> >
          >

Weblogic transaction problem

Hi Friends,
When i run my application i 'm getting the following exception.
weblogic.transaction.internal.TimedOutException: Transact
on timed out after 33 seconds
is there any way to explicitly specify the transaction time in weblogic ?
please let me know.
rgds
Mohan S

http://edocs.bea.com/wls/docs61/ejb/reference.html#1072610

Nullpointer in 'weblogic.transaction.internal.CoordinatorImpl

          I am using Weblogic 6.1 SP4 on JDK 1.3.1 on AIX.
          My server has a transacted EJB which accesses Oracle and DB2 databases. I have
          been running my application for several months.
          Suddenly, yesterday it starting spitting out these exceptions a few times a minute.
          I cannot find the configuration change I made that would have caused this to
          suddenly start appearing. My code has not changed in 2 weeks.
          Has anyone seen this error before? Does anyone know what causes this, so that
          I can narrow my search?
          Thanks for your help,
          Tania
          ####<Mar 4, 2003 12:35:48 PM CST> <Warning> <Dispatcher> <ksp12025> <cuAS01> <ExecuteThread:
          '5' for queue: 'default'> <system> <> <000000> <RuntimeException thrown by rmi
          server: 'weblogic.rmi.internal.BasicServerRef@105 - jvmid: '-4285102758410085945S:10.1.21.21:[18120,18120,18121,18121,18120,18121,-1]:qdomain4:cuAS01',
          oid: '261', implementation: 'weblogic.transaction.internal.CoordinatorImpl@311671da''>
          java.lang.NullPointerException
          at weblogic.transaction.internal.ServerResourceInfo.isAccessibleAtAndAssignableTo(ServerResourceInfo.java(Compiled
          Code))
          at weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(ServerTransactionImpl.java(Compiled
          Code))
          at weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(ServerTransactionImpl.java(Compiled
          Code))
          at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java(Compiled
          Code))
          at weblogic.transaction.internal.SubCoordinatorImpl.startCommit(SubCoordinatorImpl.java(Compiled
          Code))
          at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown
          Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java(Compiled
          Code))
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java(Compiled
          Code))
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java(Compiled
          Code))
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled Code))
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


          Thanks,
          The problem did clear up when the Unix server had to get bounced. I believe it
          was bounced for an unrelated issue.
          The one thing I noticed was that there were a couple of copies of my EJBs in the
          wlnotdelete directory that the server had been previously compliaining about.
          They went away after the Unix server was restarted and the NullPointer problem
          went away.
          We plan to upgrade to 7.1 soon, but will try to move to SP5 if we need to sooner.
          Thanks for your help.
          Tania Rhinehart
          Rajesh Mirchandani <[email protected]> wrote:
          >This is fixed in SP5. Open a case with [email protected] and reference
          >CR092301.
          >
          >Slava Imeshev wrote:
          >
          >> Hi Tania,
          >>
          >> I think you need to contact BEA support at [email protected]
          >>
          >> Regards,
          >>
          >> Slava Imeshev
          >>
          >> "Tania Rhinehart" <[email protected]> wrote in message
          >> news:[email protected]...
          >> >
          >> > I am using Weblogic 6.1 SP4 on JDK 1.3.1 on AIX.
          >> > My server has a transacted EJB which accesses Oracle and DB2 databases.
          > I
          >> have
          >> > been running my application for several months.
          >> > Suddenly, yesterday it starting spitting out these exceptions a few
          >times
          >> a minute.
          >> > I cannot find the configuration change I made that would have caused
          >this
          >> to
          >> > suddenly start appearing. My code has not changed in 2 weeks.
          >> >
          >> > Has anyone seen this error before? Does anyone know what causes
          >this, so
          >> that
          >> > I can narrow my search?
          >> >
          >> > Thanks for your help,
          >> > Tania
          >> >
          >> > ####<Mar 4, 2003 12:35:48 PM CST> <Warning> <Dispatcher> <ksp12025>
          >> <cuAS01> <ExecuteThread:
          >> > '5' for queue: 'default'> <system> <> <000000> <RuntimeException
          >thrown by
          >> rmi
          >> > server: 'weblogic.rmi.internal.BasicServerRef@105 - jvmid:
          >> '-4285102758410085945S:10.1.21.21:[18120,18120,18121,18121,18120,18121,-1]:q
          >> domain4:cuAS01',
          >> > oid: '261', implementation:
          >> 'weblogic.transaction.internal.CoordinatorImpl@311671da''>
          >> >
          >> > java.lang.NullPointerException
          >> > at
          >> weblogic.transaction.internal.ServerResourceInfo.isAccessibleAtAndAssignable
          >> To(ServerResourceInfo.java(Compiled
          >> > Code))
          >> > at
          >> weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(Se
          >> rverTransactionImpl.java(Compiled
          >> > Code))
          >> > at
          >> weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(Se
          >> rverTransactionImpl.java(Compiled
          >> > Code))
          >> > at
          >> weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransa
          >> ctionImpl.java(Compiled
          >> > Code))
          >> > at
          >> weblogic.transaction.internal.SubCoordinatorImpl.startCommit(SubCoordinatorI
          >> mpl.java(Compiled
          >> > Code))
          >> > at
          >> weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown
          >> > Source)
          >> > at
          >> weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java(Compiled
          >> > Code))
          >> > at
          >> weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java(Compi
          >> led
          >> > Code))
          >> > at
          >> weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java(C
          >> ompiled
          >> > Code))
          >> > at
          >> weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled Code))
          >> > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >> >
          >
          >--
          >Rajesh Mirchandani
          >Developer Relations Engineer
          >BEA Support
          >
          >

Weblogic.transaction.XAException: XAER_RMERR

We have JMS adapter product which uses our own transaction manager to manage an XA global transaction. Using this product we can configure a XA connection and able to produce a message to JMS Queue. Our JMS adapter product works fine with almost all other JMS provider (Sonic, webspere etc) except weblogic. I am using weblogic 9.2. In our code we use to invoke the XAResource() as below
          ((XAQueueSession)queueSession).getXAResource()
          but this throws an error as "can only be called from server". I learnt that in client JVM you can not call getXAResource API directly, rather we should use TxHelper.getClientInterposedTransactionManager(context, serverName). We had introduced following code.
          InterposedTransactionManager itm = TxHelper.getClientInterposedTransactionManager(ctx1, "examplesServer");
          xaResource = itm.getXAResource();
          The above code works fine. Now I am getting XAResource object. But when I produce a message to weblogic JMS Queue, I get the following exception
          weblogic.transaction.XAException: XAER_RMERR : A resource manager error has occured in the transaction branch. ClientTM[examplesServer+172.31.91.57:7001+wl_server+t3+].XAResource.commit() fails.
          at weblogic.transaction.internal.XAResourceHelper.throwXAException(XAResourceHelper.java:172)
          at weblogic.transaction.internal.TransactionManagerImpl$TMXAResource.commit(TransactionManagerImpl.java:993)
          at weblogic.transaction.internal.ClientTransactionManagerImpl$ClientTMXAResource.commit(ClientTransactionManagerImpl.java:136)
          at com.wm.app.b2b.server.jca.transactions.Tran.commit(Tran.java:209)
          at com.wm.app.b2b.server.jca.transactions.Tran.delistResource(Tran.java:482)
          at com.wm.app.b2b.server.jca.transactions.TransactionImpl.delistResource(TransactionImpl.java:89)
          We are using JDK1.5. I am not sure why we are getting the above exception. Our JMS adapter code works fine with almost all other JMS provider even with XA transaction support. The problem is only with Weblogic JMS server.
          Any help on this would be appreciated.
          Thanks,
          Sagar

As per the first exception, XA resource enlistment with foreign TMs is only supported on the server - so you can either use WebLogic transactions, or run the adapter on a WL server. If you'd like to see enhancements in this area, it would help if you contacted WebLogic customer support and asked them to work with the WebLogic JMS product manager (Dave Dabelus).
          Tom

Weblogic/transaction/internal/TransactionHelperImpl class not found error

Hi All,
I am getting the follwing excepition while running the application.
which jar i need to add in the class path. I am using weblogic 10.0 sever.
pls help as soon as possible.
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/transaction/internal/TransactionHelperImpl
at weblogic.jndi.spi.EnvironmentManager$DefaultFactoryMaker.<clinit>(EnvironmentManager.java:26)
at weblogic.jndi.spi.EnvironmentManager.getInstance(EnvironmentManager.java:48)
at weblogic.jndi.Environment.getContext(Environment.java:307)
at weblogic.jndi.Environment.getContext(Environment.java:277)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.deceval.security.businessobjects.ServiceLocator.getContext(ServiceLocator.java:66)
at com.deceval.security.businessobjects.ServiceLocator.getSecurityServerMgrSO(ServiceLocator.java:138)
at com.deceval.security.securityinterface.SecuritySubSystemWin.<init>(SecuritySubSystemWin.java:121)
at com.deceval.security.securitywindow.StartClass.<init>(StartClass.java:29)
at com.deceval.security.securitywindow.StartClass.main(StartClass.java:47)
Press any key to continue . . .
thanks in advance
krishna

This error line does hint that you do have the required JARs in the classpath but there may be version different. If jar is missing you would have NoClassDefFound Error. But it say method signature not found. May be the jar that you are using do not have this method. Try using other version of the jar. Incase if you have like any java decompiler, you can always open this .class file and see if this method signature exists in that class.
Caused by: java.lang.NoSuchMethodError: org.objectweb.asm.ClassVisitor.visit(IILjava/lang/String;Ljava/lang/String;[Ljava/lang/String;Ljava/lang/String;)V
I do not know anything about asm, but just incase if this class happens to exist in any other package also but with different APIs (older versions) and you are referring them first. Usually this happens if we have same class with diff versions in diff jars and the order in which this class gets loaded. So if you have this same class but latest version put those JARs in the first before asm jars. You gave list of some packages, put the asm package in the end and see if that helps. Its just a hint as we do run into these kind of issues specially with diff version os Struts jars that we use everyday with weblogic.
HTH
Ravi Jegga

Weblogic.transaction.RollbackException - Could not prepare resource

Hi All,
My WLI application transfers data from CrossAccess to Oracle. Once the record is inserted in the Oracle database. A record in another oracle database is updated.
I am using a session bean to perform this task. With in SessionBean I am using UserTransaction. Once all the data is transfered from CrossAccess to Oracle database, I am commiting the user transaction.
While commiting the user transaction I am getting the following Exception. The exception occurs very rarely. Once the server is bounced everything works fine.
The Application server is Weblogic Integeration8.1 SP4 and database is Oralce 9.
oracle.jdbc.xa.OracleXAException
     at oracle.jdbc.xa.client.OracleXAResource.prepare(Ljavax.transaction.xa.Xid; )I(OracleXAResource.java:558)
     at weblogic.jdbc.wrapper.VendorXAResource.prepare(Ljavax.transaction.xa.Xid; )I(VendorXAResource.java:70)
     at weblogic.jdbc.jta.DataSource.prepare(Ljavax.transaction.xa.Xid; )I(DataSource.java:890)
     at weblogic.transaction.internal.XAServerResourceInfo.prepare(Lweblogic.transaction.internal.ServerTransactionImpl;Ljavax.transaction.xa.Xid; )I(XAServerResourceInfo.java:1234)
     at weblogic.transaction.internal.XAServerResourceInfo.prepare(Lweblogic.transaction.internal.ServerTransactionImpl; )I(XAServerResourceInfo.java:441)
     at weblogic.transaction.internal.ServerSCInfo$1.execute(Lweblogic.kernel.ExecuteThread; )V(ServerSCInfo.java:253)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest; )V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread; )V(Unknown Source)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Could not prepare resource 'weblogic.jdbc.jta.DataSource - with nested exception:
[oracle.jdbc.xa.OracleXAException]
     at weblogic.transaction.internal.TransactionImpl.throwRollbackException()V(TransactionImpl.java:1683)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit()V(ServerTransactionImpl.java:325)
     at weblogic.transaction.internal.ServerTransactionImpl.commit()V(ServerTransactionImpl.java:246)
     at weblogic.transaction.internal.TransactionManagerImpl.commit()V(TransactionManagerImpl.java:303)
     at com.xyz.inventory.dcreceipts.ejb.DCReceiptsGOLDBean.perform(Lcom.xyz.integration.framework.TypedMap; )V(DCReceiptsGOLDBean.java:1072)
     at com.xyz.inventory.dcreceipts.ejb.DCReceiptsGOLDBean_zf5z70_EOImpl.perform(Lcom.xyz.integration.framework.TypedMap; )V(DCReceiptsGOLDBean_zf5z70_EOImpl.java:46)
     at com.xyz.inventory.dcreceipts.process.DCReceiptsProcess.perform()V(DCReceiptsProcess.jpd:442)
     at com.xyz.inventory.dcreceipts.process.DCReceiptsProcess_wf$ImplPerform6.invoke(Lcom.bea.wli.bpm.runtime.ProcessState; )V(DCReceiptsProcess_wf.java:68)
     at com.bea.wli.bpm.runtime.Perform.execute(Lcom.bea.wli.bpm.runtime.ProcessState; )Lcom.bea.wli.bpm.runtime.Activity;(Perform.java:32)
     at com.bea.wli.bpm.runtime.Receive.messageDelivery(Lcom.bea.wli.bpm.runtime.ProcessState;[Ljava.lang.Object; )Ljava.lang.Object;(Receive.java:91)
     at com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Lcom.bea.wli.bpm.runtime.ProcessState;[Ljava.lang.Object; )Ljava.lang.Object;(Receive.java:71)
     at com.bea.wli.bpm.runtime.ProcessState.processMessage(I[Ljava.lang.Object;Z)Ljava.lang.Object;(ProcessState.java:166)
     at com.xyz.inventory.dcreceipts.process.DCReceiptsProcess_wf$_ProcessState.processMessage(I[Ljava.lang.Object;Z)Ljava.lang.Object;(DCReceiptsProcess_wf.java:204)
     at com.xyz.inventory.dcreceipts.process.DCReceiptsProcess_wf.subscription(Ljava.lang.String; )V(DCReceiptsProcess_wf.java:184)
     at jrockit.reflect.NativeMethodInvoker.invoke0(Ljava.lang.Object;ILjava.lang.Object;[Ljava.lang.Object; )Ljava.lang.Object;(Unknown Source)
     at jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object; )Ljava.lang.Object;(Unknown Source)
     at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object; )Ljava.lang.Object;(Unknown Source)
     at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
     at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(Ljava.lang.Object;[Ljava.lang.Object; )Ljava.lang.Object;(DispMethod.java:371)
     at com.bea.wlw.runtime.core.container.Invocable.invoke(Ljava.lang.Object;Ljava.lang.String;Lcom.bea.wlw.runtime.core.dispatcher.DispMethod;[Ljava.lang.Object; )Ljava.lang.Object;(Invocable.java:423)
     at com.bea.wlw.runtime.core.container.Invocable.invoke(Lcom.bea.wlw.runtime.core.dispatcher.DispMethod;[Ljava.lang.Object; )Ljava.lang.Object;(Invocable.java:396)
     at com.bea.wlw.runtime.core.container.Invocable.invoke(Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.dispatcher.InvokeResult;(Invocable.java:248)
     at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.dispatcher.InvokeResult;(BaseContainerBean.java:224)
     at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.dispatcher.InvokeResult;(SLSBContainerBean.java:103)
     at com.bea.wlwgen.DCReceiptsProcessSLSBContImpl.subscription(Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.dispatcher.InvokeResult;(DCReceiptsProcessSLSBContImpl.java:25)
     at com.bea.wlwgen.StatelessContainer_nj08aw_ELOImpl.subscription(Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.dispatcher.InvokeResult;(StatelessContainer_nj08aw_ELOImpl.java:99)
     at com.bea.wlwgen.DCReceiptsProcessSLSBContAdpt.invokeOnBean(Ljava.lang.Object;Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.dispatcher.InvokeResult;(DCReceiptsProcessSLSBContAdpt.java:53)
     at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.request.Response;(BaseDispatcherBean.java:153)
     at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.run()Ljava.lang.Object;(BaseDispatcherBean.java:85)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedExceptionAction; )Ljava.lang.Object;(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedExceptionAction; )Ljava.lang.Object;(SecurityManager.java:147)
     at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.request.Response;(BaseDispatcherBean.java:50)

Satish Chandra wrote:
Hi All,
My WLI application transfers data from CrossAccess to Oracle. Once the record is inserted in the Oracle database. A record in another oracle database is updated.
I am using a session bean to perform this task. With in SessionBean I am using UserTransaction. Once all the data is transfered from CrossAccess to Oracle database, I am commiting the user transaction.
While commiting the user transaction I am getting the following Exception. The exception occurs very rarely. Once the server is bounced everything works fine.
The Application server is Weblogic Integeration8.1 SP4 and database is Oralce 9.
oracle.jdbc.xa.OracleXAException
     at oracle.jdbc.xa.client.OracleXAResource.prepare(Ljavax.transaction.xa.Xid; )I(OracleXAResource.java:558)Hi. This would involve a few steps to debug. I recommend you open
an official support case to get orchestrated official support.
Joe
     at weblogic.jdbc.wrapper.VendorXAResource.prepare(Ljavax.transaction.xa.Xid; )I(VendorXAResource.java:70)
     at weblogic.jdbc.jta.DataSource.prepare(Ljavax.transaction.xa.Xid; )I(DataSource.java:890)
     at weblogic.transaction.internal.XAServerResourceInfo.prepare(Lweblogic.transaction.internal.ServerTransactionImpl;Ljavax.transaction.xa.Xid; )I(XAServerResourceInfo.java:1234)
     at weblogic.transaction.internal.XAServerResourceInfo.prepare(Lweblogic.transaction.internal.ServerTransactionImpl; )I(XAServerResourceInfo.java:441)
     at weblogic.transaction.internal.ServerSCInfo$1.execute(Lweblogic.kernel.ExecuteThread; )V(ServerSCInfo.java:253)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest; )V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread; )V(Unknown Source)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Could not prepare resource 'weblogic.jdbc.jta.DataSource - with nested exception:
[oracle.jdbc.xa.OracleXAException]
     at weblogic.transaction.internal.TransactionImpl.throwRollbackException()V(TransactionImpl.java:1683)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit()V(ServerTransactionImpl.java:325)
     at weblogic.transaction.internal.ServerTransactionImpl.commit()V(ServerTransactionImpl.java:246)
     at weblogic.transaction.internal.TransactionManagerImpl.commit()V(TransactionManagerImpl.java:303)
     at com.xyz.inventory.dcreceipts.ejb.DCReceiptsGOLDBean.perform(Lcom.xyz.integration.framework.TypedMap; )V(DCReceiptsGOLDBean.java:1072)
     at com.xyz.inventory.dcreceipts.ejb.DCReceiptsGOLDBean_zf5z70_EOImpl.perform(Lcom.xyz.integration.framework.TypedMap; )V(DCReceiptsGOLDBean_zf5z70_EOImpl.java:46)
     at com.xyz.inventory.dcreceipts.process.DCReceiptsProcess.perform()V(DCReceiptsProcess.jpd:442)
     at com.xyz.inventory.dcreceipts.process.DCReceiptsProcess_wf$ImplPerform6.invoke(Lcom.bea.wli.bpm.runtime.ProcessState; )V(DCReceiptsProcess_wf.java:68)
     at com.bea.wli.bpm.runtime.Perform.execute(Lcom.bea.wli.bpm.runtime.ProcessState; )Lcom.bea.wli.bpm.runtime.Activity;(Perform.java:32)
     at com.bea.wli.bpm.runtime.Receive.messageDelivery(Lcom.bea.wli.bpm.runtime.ProcessState;[Ljava.lang.Object; )Ljava.lang.Object;(Receive.java:91)
     at com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Lcom.bea.wli.bpm.runtime.ProcessState;[Ljava.lang.Object; )Ljava.lang.Object;(Receive.java:71)
     at com.bea.wli.bpm.runtime.ProcessState.processMessage(I[Ljava.lang.Object;Z)Ljava.lang.Object;(ProcessState.java:166)
     at com.xyz.inventory.dcreceipts.process.DCReceiptsProcess_wf$_ProcessState.processMessage(I[Ljava.lang.Object;Z)Ljava.lang.Object;(DCReceiptsProcess_wf.java:204)
     at com.xyz.inventory.dcreceipts.process.DCReceiptsProcess_wf.subscription(Ljava.lang.String; )V(DCReceiptsProcess_wf.java:184)
     at jrockit.reflect.NativeMethodInvoker.invoke0(Ljava.lang.Object;ILjava.lang.Object;[Ljava.lang.Object; )Ljava.lang.Object;(Unknown Source)
     at jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object; )Ljava.lang.Object;(Unknown Source)
     at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object; )Ljava.lang.Object;(Unknown Source)
     at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
     at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(Ljava.lang.Object;[Ljava.lang.Object; )Ljava.lang.Object;(DispMethod.java:371)
     at com.bea.wlw.runtime.core.container.Invocable.invoke(Ljava.lang.Object;Ljava.lang.String;Lcom.bea.wlw.runtime.core.dispatcher.DispMethod;[Ljava.lang.Object; )Ljava.lang.Object;(Invocable.java:423)
     at com.bea.wlw.runtime.core.container.Invocable.invoke(Lcom.bea.wlw.runtime.core.dispatcher.DispMethod;[Ljava.lang.Object; )Ljava.lang.Object;(Invocable.java:396)
     at com.bea.wlw.runtime.core.container.Invocable.invoke(Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.dispatcher.InvokeResult;(Invocable.java:248)
     at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.dispatcher.InvokeResult;(BaseContainerBean.java:224)
     at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.dispatcher.InvokeResult;(SLSBContainerBean.java:103)
     at com.bea.wlwgen.DCReceiptsProcessSLSBContImpl.subscription(Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.dispatcher.InvokeResult;(DCReceiptsProcessSLSBContImpl.java:25)
     at com.bea.wlwgen.StatelessContainer_nj08aw_ELOImpl.subscription(Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.dispatcher.InvokeResult;(StatelessContainer_nj08aw_ELOImpl.java:99)
     at com.bea.wlwgen.DCReceiptsProcessSLSBContAdpt.invokeOnBean(Ljava.lang.Object;Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.dispatcher.InvokeResult;(DCReceiptsProcessSLSBContAdpt.java:53)
     at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.request.Response;(BaseDispatcherBean.java:153)
     at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.run()Ljava.lang.Object;(BaseDispatcherBean.java:85)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedExceptionAction; )Ljava.lang.Object;(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedExceptionAction; )Ljava.lang.Object;(SecurityManager.java:147)
     at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(Lcom.bea.wlw.runtime.core.request.Request; )Lcom.bea.wlw.runtime.core.request.Response;(BaseDispatcherBean.java:50)

Weblogic.transaction.RollbackException:

Hi All,
We are using a JMS bridge in our senario.The Flow is as follows. Message is been posted in a queue(JMS Queue)
and the host Queue recevies thye message from there it is configured with a bridge where it is targeted to different weblogic server's Queue and whlie transfering the messege from one Queue to the romote queue we are getting error.
The connection between the Queue through bridge is established but after some time we are getting the above error
FYI
####<Dec 3, 2008 1:31:48 PM GMT> <Debug> <MessagingBridge> <DSK-PNQ-900617> <RefCgServer> <ExecuteThread: '8' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200006> <Messaging bridge debugging RUNTIME! Bridge MB.REF_TO_RG1 Successfully got connection to the source destination.>
We are facing the following error:-
javax.transaction.xa.XAException
javax.transaction.xa.XAException
     at weblogic.jms.backend.BEXAResource.prepare(BEXAResource.java:903)
     at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:1234)
     at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:441)
     at weblogic.transaction.internal.ServerSCInfo$1.execute(ServerSCInfo.java:253)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Bridge "MB.REF_TO_RG1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.transaction.RollbackException: Could not prepare resource 'JMS_cgJMSStore - with nested exception:
[javax.transaction.xa.XAException].)>
Please help.
Regards
Rakesh

Hi Rakesh,
You may have better luck if you post to the "WebLogic Server - General" forum?
WebLogic Server - General

Reason=weblogic.transaction.internal.AppSetRollbackOnlyException

Hi all
i am getting this exception :
Exception in obtaining connection *java.sql.SQLException: Transaction BEA1-00238595E5CABD76B51F not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]* when i am getting connection from connection pool.
i am using weblogic 9.2 server running Windows and solaris. Both place i am getting same exception.
I have this exception only with a database Oracle 9i (the same program doesn't generate this exception with database oracle 10g )
regards

Hi all
i am getting this exception :
Exception in obtaining connection *java.sql.SQLException: Transaction BEA1-00238595E5CABD76B51F not active anymore. tx status = Marked rollback. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException]* when i am getting connection from connection pool.
i am using weblogic 9.2 server running Windows and solaris. Both place i am getting same exception.
I have this exception only with a database Oracle 9i (the same program doesn't generate this exception with database oracle 10g )
regards

What does the weblogic.transaction.internal.CoordinatorImpl do?

When under a moderate to heavy load I occasionally see as much as 90% of threads in one server on a cluster working on the following request:
          weblogic.transaction.internal.CoordinatorImpl
          This was as viewed in the WLS admin console. This is not causing a problem as far as I can see but I am curious what this object does and whether it is an indicator that something needs to be looked into.
          Any ideas?
          Thanks.

George Lupanoff <[email protected]> writes:
          It coordinates transactions
          andy
          > When under a moderate to heavy load I occasionally see as much as 90% of threads in one server on a cluster working on the following request:
          > weblogic.transaction.internal.CoordinatorImpl
          >
          > This was as viewed in the WLS admin console. This is not causing a problem as far as I can see but I am curious what this object does and whether it is an indicator that something needs to be looked into.
          >
          > Any ideas?
          > Thanks.

Weblogic Transaction Rollback Illegal State

Hi,
We have 2 different components using EJBs talking to each. We have 1 session bean
from 1 component calling another session bean from the 2nd component. The 2nd component
uses transactional datasources while the 1st doesnt. We are starting to see the exception
mentioned below and have no idea why this is happening. Any help is appreciated.
Thank you.
Sincerely,
Narayan.
weblogic.transaction.RollbackException: Illegal State (Expected: preparing). Name=[EJB
Test.validateUniq(java.lang.String,java.lang.String,java.util.HashMap)],Xid=26:adc2d5c18d486979(6201489),Status=Active
(PrePrepaed),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds
left=30,activeThread=Thread[ExecuteThread: '10' for queue: 'default',5,Thread Group
for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=new,assigned=secondserver),SCInfo[domain+firstserver]=(state=pre-prepared),SCInfo[domain+secondserver]=(state=pre-prepared),properties=({weblogic.transaction.name=[EJB
Test.validateUniq(java.lang.String,java.lang.String,java.util.HashMap)], weblogic.jdbc=t3://Test:8101}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=firstserver+localhost:8301+domain+,
Resources={})],CoordinatorURL=firstserver+localhost:8301+domain+) - with nested exception:
[javax.transaction.SystemException: Illegal State (Expected: preparing). Name=[EJB
Test.validateUniq(java.lang.String,java.lang.String,java.util.HashMap)],Xid=26:adc2d5c18d486979(6201489),Status=Active
(PrePrepaed),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds
left=30,activeThread=Thread[ExecuteThread: '10' for queue: 'default',5,Thread Group
for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=new,assigned=secondserver),SCInfo[domain+firstserver]=(state=pre-prepared),SCInfo[domain+secondserver]=(state=pre-prepared),properties=({weblogic.transaction.name=[EJB
Test.validateUniq(java.lang.String,java.lang.String,java.util.HashMap)], weblogic.jdbc=t3://localhost:8101}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=firstserver+localhost:8301+domain+,
Resources={})],CoordinatorURL=firstserver+localhost:8301+domain+)] at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1475)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:263)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)

Hi,
Thanks for the replies.
Rajesh,
The 2 comps. are different manager servers on the same domain. The WL passwords are
the same.
Emmanuel,
The reason for using non-TX datasources is, because it is not possible to have 2
tx DSs in the same transaction. It gives us an error when we attempt to do that.
We use CMP or else we would like to start our TXs and end our Txs. Is there a way
around it.
Let me know if you need any more information. Any help is appreciated. Thank you.
Sincerely,
Narayan.
Rajesh Mirchandani <[email protected]> wrote:
Are the 2 components on different instances of the server on seperate/same
box?
If yes, make sure the system password for the WLS instances are the same.
Emmanuel Proulx wrote:
I must admit this exception is at best funny-looking. I don't understandit.
But if I may ask, why aren't you using a TX datasource? Is it becauseyour
database is not XA? If that's the case you can emulate XA with TX
datasources.
Another question is, why would anyone use a non-TX datasource? ;-)
Emmanuel
"Narayan" <[email protected]> wrote in message
news:[email protected]...
Hi,
We have 2 different components using EJBs talking to each. We have 1session bean
from 1 component calling another session bean from the 2nd component.
The
2nd component
uses transactional datasources while the 1st doesnt. We are starting
to
see the exception
mentioned below and have no idea why this is happening. Any help isappreciated.
Thank you.
Sincerely,
Narayan.
weblogic.transaction.RollbackException: Illegal State (Expected:preparing). Name=[EJB
>
Test.validateUniq(java.lang.String,java.lang.String,java.util.HashMap)],Xid=
26:adc2d5c18d486979(6201489),Status=Active
(PrePrepaed),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds sincebegin=0,seconds
left=30,activeThread=Thread[ExecuteThread: '10' for queue:
'default',5,Thread Group>> > for Queue:>> 'default',ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=new,assigned=secondserver),SCInfo[domain+firstserver]=(state=pre-prepared),SCInfo[dom
ain+secondserver]=(state=pre-prepared),properties=({weblogic.transaction.nam
e=[EJB
Test.validateUniq(java.lang.String,java.lang.String,java.util.HashMap)],weblogic.jdbc=t3://Test:8101}),OwnerTransactionManager=ServerTM[ServerCoordi
natorDescriptor=(CoordinatorURL=firstserver+localhost:8301+domain+,
Resources={})],CoordinatorURL=firstserver+localhost:8301+domain+) -
with
nested exception:
[javax.transaction.SystemException: Illegal State (Expected: preparing).
Name=[EJB>> >>> Test.validateUniq(java.lang.String,java.lang.String,java.util.HashMap),Xid=26:adc2d5c18d486979(6201489),Status=Active
(PrePrepaed),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds sincebegin=0,seconds
left=30,activeThread=Thread[ExecuteThread: '10' for queue:
'default',5,Thread Group>> > for Queue:>> 'default',ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=new,assigned=secondserver),SCInfo[domain+firstserver]=(state=pre-prepared),SCInfo[dom
ain+secondserver]=(state=pre-prepared),properties=({weblogic.transaction.nam
e=[EJB
Test.validateUniq(java.lang.String,java.lang.String,java.util.HashMap)],weblogic.jdbc=t3://localhost:8101}),OwnerTransactionManager=ServerTM[ServerC
oordinatorDescriptor=(CoordinatorURL=firstserver+localhost:8301+domain+,
Resources={})],CoordinatorURL=firstserver+localhost:8301+domain+)]at
weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
tionImpl.java:1475)
atweblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:263)
atweblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:190)
atweblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

Weblogic.transaction.RollbackException: Could not prepare resource 'weblogi

Hi,
          I am getting this error on wls 9.2 and not sure why.
          I have a MultiDataSource which comprises two transactional (XA) DataSources for Oracle 9.2.
          I have a UserTransaction in progress which dequeues messages from a JMS Queue and does JDBC updates using the MultiDataSource.
          Here is the stack trace (get when calling commit on UserTransaction):
          weblogic.transaction.RollbackException: Could not prepare resource 'weblogic.jdbc.wrapper.JTSXAResourceImpl
          JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = MyMultiDS
               at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1782)
               at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:331)
               at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:227)
               at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:273)
               at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:267)
          Any ideas on this ?
          I did create the MultiDataSource (MyMultiDS) as a TX DataSource.
          Thanx

j2ee iscool wrote:
          > Hi Joe,
          >
          > Many thanx for you reply. I can think of the following four stages during which a failure can occur during (transactional)interaction with RAC:
          >
          > 1.Active RAC Node Fails before the application calls commit (Application takes care of retry).
          >
          > 2.Active RAC node fails after the application calls commit and before the container(WLS) has called prepare on the RAC(Node). WLS takes care of the recovery/retry ?
          >
          > 3.Active RAC node fails after container(WLS) has called prepare on the RAC( Node ) but before commit being called. WLS takes care of the recovery/retry ?
          >
          > 4.Active RAC node fails after container(WLS) has called prepare and commit on the RAC( Node ). Oracle takes care of the recovery ?
          >
          > We are using Transactional Data Sources (Emulate 2 phase commit and Supports Global Transaction )
          > Do the above failure phases apply in this case ?
          >
          > The scenarios which you have described (?partial transacitons being committed, rolled
          > back or data locked indefinitely...? ) can occur during which of the failure stages ? Are there other failure stages which I am missing ?
          >
          >
          > Thanx a lot for your help,
          If multiple WebLogic servers are involved in the same transaction
          they must know that for a given RAC installation, each of these
          WebLogic servers do their tx work to the same RAC node. Otherwise,
          we may prepare, commit, or roll back only one of them, because
          we think the DBMS is really only one, when it's not. Oracle does
          not guarantee transaction ID uniqueness across nodes until prepare,
          so if we unwittingly address multiple RAC nodes for a given XA
          tx, the DBMSes will be quite happy about getting different, conflicting
          transactional commands with the same-named tx ID as far as we're
          concerned... Stuff like that.
          Joe

Weblogic.transaction.TimedOutException

Similar Messages

Maybe you are looking for