[ http://jira.jboss.com/jira/browse/JBMESSAGING-904?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-904: ------------------------------------- This is failing because on failover of a session we shutdownAfterProcessingCurrentTasks on the session's executor, then replace the executor. This means if an ack is retried after being put on hold after failover and ackmode is auto ack then the ack can be resumed, but before it completes and nulls the auto_ack info in the session state another delivery can be excuted - but on a different thread since we replaced the executor so it smacks into the back of the first one throws an exception and the message doesn't get delivered. The next message that actually gets delivered is then the next one and the assertion is thrown. Solution is to subclass QueuedExecutor with a new class that allows all excet currently executing task to be cleared without shutting down the QueuedExecutor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-904?page=all ] Tim Fox closed JBMESSAGING-904. ------------------------------- Resolution: Done Assignee: Tim Fox (was: Ovidiu Feodorov) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira