[
http://jira.jboss.com/jira/browse/JBMESSAGING-633?page=comments#action_12... ]
Juha Lindfors commented on JBMESSAGING-633:
-------------------------------------------
How do you know the redelivery never occurs -- your sample code keeps rethrowing the same
runtime exception until the message ends up in the DLQ.
In any case, this is a "won't fix" until AS 4.2 is out with common remoting
/ serialization library versions.
Message redelivery for EJB3 MDB's
---------------------------------
Key: JBMESSAGING-633
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-633
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.0.1.GA
Environment: Windows xp SP2, JBoss 4.0.5.GA
Reporter: Tomaz Cerar
Assigned To: Juha Lindfors
Fix For: 1.0.2.CR1
Attachments: ejb3mdbRedelivery.zip
Original Estimate: 3 days
Time Spent: 2 hours
Remaining Estimate: 2 days, 6 hours
When RuntimException is thrown in onMessage method, jboss messaging should redeliver
message.
that is at least what it says it will do:
15:51:03,357 ERROR [MessageCallbackHandler] RuntimeException was thrown from onMessage,
90625 will be redelivered
but redelivery never occurs.
This problem exists only with EJB3 MDB's with EJB 2.1 works fine.
--
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