Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

exception: Unable to use a wrapped JMS session in the transaction because two-phase commit is not available

181 views
Skip to first unread message

Carl

unread,
Dec 26, 2003, 7:29:09 PM12/26/03
to
I am getting the following exception. The exception occurs regardless of
whether the value of EnableTwoPhaseCommit for JDBCTxDataSource is true or
false.

The workaround is not to use resource ref for connection factory. However,
whether the transaction commits or rolls back, the message is always sent
and received:(

I am expecting the data not to commit and the message to be never sent when
EnableTwoPhaseCommit is true, resource ref is used or not, and transaction
is rolled back.

I will be more than happy to provide configurations or working code sample
to demonstrate this problem...

Workarounds and suggestions are most welcome.

javax.jms.JMSException: [J2EE:160055]Unable to use a wrapped JMS session in
the transaction because two-phase commit is not available
at
weblogic.deployment.jms.JMSExceptions.getJMSException(JMSExceptions.java:22)
at
weblogic.deployment.jms.WrappedTransactionalSession.enlistInExistingTransact
ion(WrappedTransactionalSession.java:146)
at
weblogic.deployment.jms.WrappedTransactionalSession.enlistInTransaction(Wrap
pedTransactionalSession.java:190)
at
weblogic.deployment.jms.WrappedMessageProducer.send(WrappedMessageProducer.j
ava:124)
at
com.malani.sem.agent.AgentFacadeBean.enqueuePerson(AgentFacadeBean.java:115)
at
com.malani.sem.agent.AgentFacade_6js8s0_EOImpl.enqueuePerson(AgentFacade_6js
8s0_EOImpl.java:46)
at com.malani.sem.agent.AgentFacade_6js8s0_EOImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:108)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjec
t.java:353)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:3
0)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
; nested exception is:
javax.jms.JMSException: [J2EE:160055]Unable to use a wrapped JMS session in
the transaction because two-phase commit is not available
at
weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108
)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:284)
at
weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
:244)
at
com.malani.sem.agent.AgentFacade_6js8s0_EOImpl_811_WLStub.enqueuePerson(Unkn
own Source)
at
com.malani.sem.agent.test.AgentFacadeTest.testProcessPerson(AgentFacadeTest.
java:26)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at
com.intellij.rt.execution.junit.TextTestRunner.main(TextTestRunner.java:12)
Caused by: javax.jms.JMSException: [J2EE:160055]Unable to use a wrapped JMS
session in the transaction because two-phase commit is not available
at
weblogic.deployment.jms.JMSExceptions.getJMSException(JMSExceptions.java:22)
at
weblogic.deployment.jms.WrappedTransactionalSession.enlistInExistingTransact
ion(WrappedTransactionalSession.java:146)
at
weblogic.deployment.jms.WrappedTransactionalSession.enlistInTransaction(Wrap
pedTransactionalSession.java:190)
at
weblogic.deployment.jms.WrappedMessageProducer.send(WrappedMessageProducer.j
ava:124)
at
com.malani.sem.agent.AgentFacadeBean.enqueuePerson(AgentFacadeBean.java:115)
at
com.malani.sem.agent.AgentFacade_6js8s0_EOImpl.enqueuePerson(AgentFacade_6js
8s0_EOImpl.java:46)
at com.malani.sem.agent.AgentFacade_6js8s0_EOImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:108)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjec
t.java:353)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:3
0)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)


Carl

unread,
Dec 28, 2003, 2:27:31 PM12/28/03
to
The problem is solved. I didn't have the XA enabled on the connection
factory:(

"Carl" <ca...@yahoo.com> wrote in message news:3fec...@newsgroups.bea.com...

utta...@gmail.com

unread,
Feb 12, 2020, 3:23:12 AM2/12/20
to
Hi Carl,

I am facing the same issue but for JMS EMS Connection factory. You can see the entire wire up logic here : https://community.tibco.com/questions/there-option-we-can-enable-xa-transaction-support-ems.

Please suggest possible solution.

Thanks,
Uttam
0 new messages