[jboss-jira] [JBoss JIRA] (JBMESSAGING-1949) JMS Error - thread is already associated with a transaction - MDB

vish vars (JIRA) issues at jboss.org
Fri Dec 27 00:59:33 EST 2013


    [ https://issues.jboss.org/browse/JBMESSAGING-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933237#comment-12933237 ] 

vish vars commented on JBMESSAGING-1949:
----------------------------------------

Any comments would be helpful
                
> JMS Error - thread is already associated with a transaction - MDB
> -----------------------------------------------------------------
>
>                 Key: JBMESSAGING-1949
>                 URL: https://issues.jboss.org/browse/JBMESSAGING-1949
>             Project: JBoss Messaging
>          Issue Type: Bug
>         Environment: jboss-5.1.0 GA
>            Reporter: vish vars
>              Labels: JMS, MDB, jboss, transactionmanager
>
> Getting the below Exception while the MDB consumes the Message from Queue.
> This ERROR results in the message getting discarded and its critical. Appreciate if there is a patch for this problem or any workaround.
> Complete Stack trace:
> 2013-11-25 00:00:08,011 ERROR [org.jboss.resource.adapter.jms.inflow.JmsServerSession] (WorkManager(2)-74) Unexpected error delivering message delegator->JBossMessage[22697371369499608]:PERSISTENT, deliveryId=256984
> java.lang.NoClassDefFoundError: org/jboss/ejb3/tx/AbstractInterceptor
>         at org.jboss.ejb3.tx.TxUtil.getApplicationException(TxUtil.java:71)
>         at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:92)
>         at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
>         at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:194)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
>         at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
>         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:80)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
>         at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
>         at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
>         at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:282)
>         at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:270)
>         at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:140)
>         at $Proxy320.onMessage(Unknown Source)
>         at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178)
>         at org.jboss.jms.client.container.ClientConsumer.callOnMessageStatic(ClientConsumer.java:160)
>         at org.jboss.jms.client.container.SessionAspect.handleRun(SessionAspect.java:831)
>         at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect_z_handleRun_836584.invoke(SessionAspect_z_handleRun_836584.java)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
>         at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
>         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
>         at org.jboss.jms.client.delegate.ClientSessionDelegate.run(ClientSessionDelegate.java)
>         at org.jboss.jms.client.JBossSession.run(JBossSession.java:199)
>         at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:234)
>         at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
>         at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>         at java.lang.Thread.run(Thread.java:662)
> 2013-11-25 00:00:10,530 WARN  [org.jboss.system.server.profileservice.hotdeploy.HDScanner] (HDScanner) Scan failed
> java.io.IOException: Error listing files: /home/JBOSS/jboss-5.1.0.GA/server/default/deploy/management/console-mgr.sar/META-INF
>         at org.jboss.virtual.plugins.context.file.FileHandler.getChildren(FileHandler.java:225)
>         at org.jboss.virtual.plugins.context.AbstractVFSContext.getChildren(AbstractVFSContext.java:219)
>         at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:336)
>         at org.jboss.virtual.plugins.context.AbstractVFSContext.visit(AbstractVFSContext.java:306)
>         at org.jboss.virtual.VFS.visit(VFS.java:421)
>         at org.jboss.virtual.VirtualFile.visit(VirtualFile.java:437)
>         at org.jboss.virtual.VirtualFile.getChildren(VirtualFile.java:386)
>         at org.jboss.deployers.vfs.spi.structure.modified.MetaDataStructureModificationChecker.hasStructureBeenModifed(MetaDataStructureModificationChecker.java:144)
>         at org.jboss.deployers.vfs.spi.structure.modified.MetaDataStructureModificationChecker.hasStructureBeenModified(MetaDataStructureModificationChecker.java:115)
>         at org.jboss.deployers.vfs.spi.structure.modified.MetaDataStructureModificationChecker.hasStructureBeenModifed(MetaDataStructureModificationChecker.java:84)
>         at org.jboss.deployers.vfs.spi.structure.modified.SynchWrapperModificationChecker.hasStructureBeenModifed(SynchWrapperModificationChecker.java:83)
>         at org.jboss.deployers.vfs.spi.structure.modified.SynchWrapperModificationChecker.hasStructureBeenModifed(SynchWrapperModificationChecker.java:83)
>         at org.jboss.deployers.vfs.spi.structure.modified.AbstractStructureModificationChecker.hasStructureBeenModified(AbstractStructureModificationChecker.java:195)
>         at org.jboss.deployers.vfs.spi.structure.modified.AbstractStructureModificationChecker.hasStructureBeenModified(AbstractStructureModificationChecker.java:138)
>         at org.jboss.system.server.profileservice.repository.HotDeploymentRepository.getModifiedDeployments(HotDeploymentRepository.java:120)
>         at org.jboss.system.server.profile.repository.AbstractProfile.getModifiedDeployments(AbstractProfile.java:128)
>         at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:336)
>         at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>         at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>         at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>         at java.lang.Thread.run(Thread.java:662)
> 2013-11-25 00:00:14,620 ERROR [org.jboss.resource.adapter.jms.inflow.JmsServerSession] (WorkManager(2)-95) org.jboss.resource.adapter.jms.inflow.JmsServerSession$DemarcationStrategyFactory at 54ae94 error creating transaction demarcation
> javax.transaction.NotSupportedException: BaseTransaction.checkTransactionState - [com.arjuna.ats.internal.jta.transaction.arjunacore.alreadyassociated] [com.arjuna.ats.internal.jta.transaction.arjunacore.alreadyassociated] thread is already associated with a transaction!
>         at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:80)
>         at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.begin(BaseTransactionManagerDelegate.java:65)
>         at org.jboss.resource.adapter.jms.inflow.JmsServerSession$XATransactionDemarcationStrategy.<init>(JmsServerSession.java:560)
>         at org.jboss.resource.adapter.jms.inflow.JmsServerSession$DemarcationStrategyFactory.getStrategy(JmsServerSession.java:295)
>         at org.jboss.resource.adapter.jms.inflow.JmsServerSession.createTransactionDemarcation(JmsServerSession.java:252)
>         at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:224)
>         at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
>         at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>         at java.lang.Thread.run(Thread.java:662)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list