I can confirm that the stack trace is related to the pre-ack mode. I just
changed this to DUPS_OK in the client and set pre-ack to false in the server
and restarted the apps and server and instead of the stack trace I now see
messages like this in the log:
"Message has expired. No expiry queue
Thanks for the quick reply. I created a Jira issue here:
https://jira.jboss.org/jira/browse/JBMESSAGING-1679
Let me know if you need any more info or need me to test a fix. I noticed that
in the "create issue" screen there is a link "READ THIS BEFORE ENTERING NEW
REPORTS." which links to a 404
Looks like a bug.
It seems that messages with an expiry set do not currently work well with
pre-ack.
Can you file a JIRA? Should be an easy fix.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242246#4242246
Reply to the post :
http://www.jboss.org/index.ht
