[ https://issues.jboss.org/browse/JBMESSAGING-1876?page=com.atlassian.jira.... ] Yong Hao Gao commented on JBMESSAGING-1876: ------------------------------------------- We give the pre/postDeliver() a minTimeoutProcessTime (configurable) For client ack and Tx ack mode, the pre/postDeliver() won't take much time to finish as they don't make remote invocations. However, when timeout + minTimeoutProcessTime expires and the pre/postDeliver() is still not finished, we need to make a decision. There are 4 cases we need to consider, based on 4 ack modes. 1. Transaction mode: We mark the transaction as rolled back and return the message to the application. When the transaction is committed, it results in rollback. 2. Client ACK mode: We just return the message to the application and that'll be fine. 3. AUTO_ACK mode: We returns the message to application. If the postDeliver() failed to ack the message, log a warning message. And the message may be re-delivered. 4 DUPS_OK mode: Same as AUTO_ACK. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBMESSAGING-1876?page=com.atlassian.jira.... ] Yong Hao Gao resolved JBMESSAGING-1876. --------------------------------------- Resolution: Done -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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." -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBMESSAGING-1876?page=com.atlassian.jira.... ] Yong Hao Gao closed JBMESSAGING-1876. ------------------------------------- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira