[ http://jira.jboss.com/jira/browse/JBMESSAGING-852?page=all ] Tim Fox updated JBMESSAGING-852: -------------------------------- Description: If an exception is thrown from a call to acknowledge, then the unacked message data is not cleared out, this cause the next call to postDeliver to give the exception: ERROR 2007-02-15 17:49:52,703 [Manager Queue Seven.1.0] org.jboss.jms.client.remoting.MessageCallbackHandler: Failed to deliver message javax.jms.IllegalStateException: Should only be one entry in list. There are 2 at org.jboss.jms.client.container.SessionAspect.handlePostDeliver(SessionAspect.java:203) at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect6.invoke(SessionAspect6.java) was: If an exception is thrown from a call to acknowledge, then the unacked message data is not cleared out, this cause the next call to postDeliver to give the exception: -- 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-852?page=comments#action_12... ] Clebert Suconic commented on JBMESSAGING-852: --------------------------------------------- just a FYI, the change here caused JBMESSAGING-862 -- 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