[
https://issues.jboss.org/browse/JBMESSAGING-1876?page=com.atlassian.jira....
]
Yong Hao Gao reopened JBMESSAGING-1876:
---------------------------------------
from Kevin:
"I have now got to the bottom of it, there is a race between the
background thread and the transaction rollback.
All of the successful tests have the background thread adding the
delivery to the resource manager *before* the rollback occurs, the
failure has the resource being added to the manager *after* rollback.
The result is that the message ack is added to the *next* active
transaction on that session, not the current one, and will be lost."
The fix for JBMESSAGING-1850 may cause message loss
---------------------------------------------------
Key: JBMESSAGING-1876
URL:
https://issues.jboss.org/browse/JBMESSAGING-1876
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Facade
Affects Versions: 1.4.0.SP3.CP12, 1.4.8.GA
Reporter: Yong Hao Gao
Assignee: Yong Hao Gao
Fix For: 1.4.0.SP3.CP13, 1.4.8.SP1
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira