[jboss-jira] [JBoss JIRA] Reopened: (JBMESSAGING-1786) Message stuck caused by rolling back the transaction

Howard Gao (JIRA) jira-events at lists.jboss.org
Thu Mar 11 00:58:37 EST 2010


     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard Gao reopened JBMESSAGING-1786:
-------------------------------------



reopen to update versions

> Message stuck caused by rolling back the transaction
> ----------------------------------------------------
>
>                 Key: JBMESSAGING-1786
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1786
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core
>    Affects Versions: 1.4.0.SP3.CP09
>            Reporter: Toshiya Kobayashi
>            Assignee: Howard Gao
>             Fix For: 1.4.0.SP3.CP10
>
>
> Say, you have 2 JBoss instances, one is JMS server and the other is app server which consumes messages from the JMS server with XA.
> If the app server is killed (kill -9) after prepare phase and restarts, recovery will kick in and the transaction will be rolled back.
> The rollback process does rollback the database (JMB_MSG_REF etc.), but doesn't restore/cancel in-memory state of the queue (e.g. ChannelSupport.messageRefs, ChannelSupport.deliveryCount). Eventually the message will be stuck in the queue. Restarting JMS server will make the message alive again because the database is correctly rolled back.

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

        



More information about the jboss-jira mailing list