28/06/06 - SCJP - 69%, 05/06/07 - SCWCD - 92%, 28/02/08 - IBM DB2 v9 Fundamentals (Exam 730) - 87%, 18/11/08 - IBM DB2 v9 DBA (Exam 731) - 89%, 26/02/11 - SCBCD - 88%
My free books and tutorials: http://www.slideshare.net/krizsan
SCEA | SCBCD | SCWCD | SCJP - The kSpace
Ivan Krizsan wrote:
I have been thinking about this today
Ivan Krizsan wrote:
- Periodically, perhaps using an EJB timer, poll the failed attempts queue for messages that are old enough to be retried.
Ivan Krizsan wrote:
The fact that MDBs seem to be unable to roll back a received message unless throwing an exception causes problems in both your example and the solution outline I have been thinking of.
k space wrote:JMS spec does not mention anything about the redelivery. It is entirely up to the JMS server. Please refer to this article about the JMS message redelievery
28/06/06 - SCJP - 69%, 05/06/07 - SCWCD - 92%, 28/02/08 - IBM DB2 v9 Fundamentals (Exam 730) - 87%, 18/11/08 - IBM DB2 v9 DBA (Exam 731) - 89%, 26/02/11 - SCBCD - 88%
28/06/06 - SCJP - 69%, 05/06/07 - SCWCD - 92%, 28/02/08 - IBM DB2 v9 Fundamentals (Exam 730) - 87%, 18/11/08 - IBM DB2 v9 DBA (Exam 731) - 89%, 26/02/11 - SCBCD - 88%
Mark Garland wrote:
Ivan Krizsan wrote:
The fact that MDBs seem to be unable to roll back a received message unless throwing an exception causes problems in both your example and the solution outline I have been thinking of.
I'm not sure that this is quite right. You can simply use the context and call setRollbackOnly(), and the container will do the rest for you.
My free books and tutorials: http://www.slideshare.net/krizsan
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |