You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Mike Mole (Commented) (JIRA)" <ji...@apache.org> on 2011/12/15 21:23:30 UTC
[jira] [Commented] (AMQ-3602) javax.jms.JMSException: The resource
is allready being used in transaction context.
[ https://issues.apache.org/jira/browse/AMQ-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170468#comment-13170468 ]
Mike Mole commented on AMQ-3602:
--------------------------------
I think this may be a duplicate of https://issues.apache.org/jira/browse/AMQ-3465 which is fixed for 5.6.0.
> javax.jms.JMSException: The resource is allready being used in transaction context.
> ------------------------------------------------------------------------------------
>
> Key: AMQ-3602
> URL: https://issues.apache.org/jira/browse/AMQ-3602
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.5.0, 5.5.1
> Environment: SLES11sp1 64bits, Glassfish 2.1.1, activemq-5.5.0, jdk6
> Linux (unknow), Glassfish 3.1, activemq-5.5.1
> Reporter: Nicolas De Amicis
>
> My error code:
> {quote}javax.ejb.EJBException: nested exception is: javax.jms.JMSException: The resource is allready being used in transaction context.
> javax.jms.JMSException: The resource is allready being used in transaction context.
> at org.apache.activemq.ra.ManagedTransactionContext.setUseSharedTxContext(ManagedTransactionContext.java:47)
> at org.apache.activemq.ra.ManagedSessionProxy.setUseSharedTxContext(ManagedSessionProxy.java:67)
> at org.apache.activemq.ra.ManagedConnectionProxy.createSessionProxy(ManagedConnectionProxy.java:122)
> at org.apache.activemq.ra.ManagedConnectionProxy.createSession(ManagedConnectionProxy.java:105)
> at ch.no.prod.mdb.ToProdMDB.publish(ToProdMDB.java:163)
> at ch.no.prod.mdb.ToProdMDB.onMessage(ToProdMDB.java:107)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1011)
> at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:175)
> at com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2929)
> at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:4020)
> at com.sun.ejb.containers.MessageBeanContainer.deliverMessage(MessageBeanContainer.java:1111)
> at com.sun.ejb.containers.MessageBeanListenerImpl.deliverMessage(MessageBeanListenerImpl.java:74)
> at com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:179)
> at $Proxy62.onMessage(Unknown Source)
> at org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.onMessage(MessageEndpointProxy.java:123)
> at org.apache.activemq.ra.MessageEndpointProxy.onMessage(MessageEndpointProxy.java:64)
> at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:833)
> at org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:169)
> at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:77)
> at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:555)
> javax.ejb.EJBException: nested exception is: javax.jms.JMSException: The resource is allready being used in transaction context.
> at ch.no.prod.mdb.ToProdMDB.publish(ToProdMDB.java:279)
> at ch.no.prod.mdb.ToProdMDB.onMessage(ToProdMDB.java:107)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at com.sun.enterprise.security.application.EJBSecurityManager.runMethod(EJBSecurityManager.java:1011)
> at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:175)
> at com.sun.ejb.containers.BaseContainer.invokeTargetBeanMethod(BaseContainer.java:2929)
> at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:4020)
> at com.sun.ejb.containers.MessageBeanContainer.deliverMessage(MessageBeanContainer.java:1111)
> at com.sun.ejb.containers.MessageBeanListenerImpl.deliverMessage(MessageBeanListenerImpl.java:74)
> at com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:179)
> at $Proxy62.onMessage(Unknown Source)
> at org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.onMessage(MessageEndpointProxy.java:123)
> at org.apache.activemq.ra.MessageEndpointProxy.onMessage(MessageEndpointProxy.java:64)
> at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:833)
> at org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:169)
> at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:77)
> at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:555){quote}
>
> And more informations found on web : http://osdir.com/ml/general/2011-11/msg29999.html and http://activemq.2283324.n4.nabble.com/Suspect-a-race-condition-in-TransactionContext-td3780046.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira