[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1791) ConcurrentModificationException at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeTransactionally

[Howard Gao (JIRA)]

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

Howard Gao commented on JBMESSAGING-1791:
-----------------------------------------

Hi Tamas,

1.4.0.SP3 is very old version. The current 1.4.0.SP3.CP10. Can you try it? There are a lot of bug fixes since 1.4.0.SP3. The issue you are seeing probably have been fixed already.

If you still having problem after upgrading, please post the server.log here.

Please note that JMS sessions should not be used concurrently. It's not thread safe as per JMS spec 1.1

Howard


> ConcurrentModificationException at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeTransactionally
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1791
>                 URL: https://jira.jboss.org/browse/JBMESSAGING-1791
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0.SP3
>         Environment: JBoss AS 4.2.3.GA Release (JBossESB 4.7)
> jboss.messaging.jmsVersion=1.1
> jboss.messaging.jmsMajorVersion=1
> jboss.messaging.jmsMinorVersion=1
> jboss.messaging.jmsProviderName=JBoss Messaging
> jboss.messaging.providerVersion=1.4.0.SP3
> jboss.messaging.providerMajorVersion=1
> jboss.messaging.providerMinorVersion=4
> jboss.messaging.providerIncrementingVersion=21
>            Reporter: Tamas Cserveny
>            Assignee: Howard Gao
>             Fix For: 1.4.0.SP3.CP11
>
>         Attachments: server.log
>
>
> Hi, 
> I found a CME in the JBoss-messageing. 
> Test scenario:
> Vanilla JBossESB 4.7 with a simple flow. (file -> queue, bridge queue to another queue, queue -> file)
> I kept this server running on a 2 core system with a load of 10 messages / sec. (ca 3kb messages).
> I received many of these exception during the test. It caused some messages to stuck into the queue, but eventually they were redelivered. (Not after 5s, but after some other messages). They were counted in the 'DeliveringCount', and stayed like that.
> Cheers,
> Tamas
> 2010-02-26 00:00:50,083 ERROR [org.jboss.jms.client.container.ClientConsumer] Failed to deliver message
> javax.jms.JMSException: There is no transaction with id LocalTx[m0r-676r546g-1-2tbmq36g-nq5p47-51zk6a]
>         at org.jboss.jms.tx.ResourceManager.addAck(ResourceManager.java:186)
>         at org.jboss.jms.client.container.SessionAspect.handlePreDeliver(SessionAspect.java:293)
>         at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect19.invoke(SessionAspect19.java)
>         at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_5548846795541436298.invokeNext(ClientSessionDelegate$preDeliver_5548846795541436298.java)
>         at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
>         at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
>         at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_5548846795541436298.invokeNext(ClientSessionDelegate$preDeliver_5548846795541436298.java)
>         at org.jboss.jms.client.delegate.ClientSessionDelegate.preDeliver(ClientSessionDelegate.java)
>         at org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:152)
>         at org.jboss.jms.client.container.ClientConsumer$ListenerRunner.run(ClientConsumer.java:976)
>         at org.jboss.messaging.util.JBMExecutor$TCLExecutor.run(JBMExecutor.java:78)
>         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
>         at java.lang.Thread.run(Thread.java:619)
> 2010-02-26 00:03:22,084 ERROR [org.jboss.messaging.util.ExceptionUtil] ConnectionEndpoint[uip-txvw446g-1-2tbmq36g-nq5p47-51zk6a] sendTransaction [f6r-ghfu546g-1-2tbmq36g-nq5p47-5
> java.util.ConcurrentModificationException
>         at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
>         at java.util.AbstractList$Itr.next(AbstractList.java:343)
>         at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeTransactionally(ServerSessionEndpoint.java:1474)
>         at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:810)
>         at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:473)
>         at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101)
>         at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N3268650789275322226.invokeNext(ConnectionAdvised$sendTransaction_N3268650789275322226.java)
>         at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira