This content has been marked as final.
Show 2 replies
-
1. Re: Msg expiration doesn't work with a msg listener on a ses
adrian.brock Apr 18, 2007 8:22 AM (in response to wolfc)You have not been listening to a word I've been saying.
// block consuming for 5 seconds Thread.sleep(5000); processed++;
If you do this, it is a not a problem for the JMS Server.
The JMS Server has given you a message when it wasn't expired.
It is your fault that you did not process it until after it expired. -
2. Re: Msg expiration doesn't work with a msg listener on a ses
weston.price Apr 18, 2007 8:28 AM (in response to wolfc)Actually, Carlo and I had a discussion about this yesterday and I believe the issue is clearer. This post is 'outdated' at this point.
Ideally the question is do we want to take action when a message has expired en route. As you pointed out in the JIRA we could simply add this as an interceptor as a QOS feature. Similarly, the adatper could do this as well but I am more inclinded to have it outside of the JCA stuff. It really is an interceptor type task.