]
Carlo de Wolf updated EJBTHREE-1239:
------------------------------------
Fix Version/s: 1.0.0-Beta7
(was: 1.0.0-Beta6)
A mechanism to shutdown JMS connections when an MDB encounters a
RuntimeException
---------------------------------------------------------------------------------
Key: EJBTHREE-1239
URL:
https://jira.jboss.org/jira/browse/EJBTHREE-1239
Project: EJB 3.0
Issue Type: Feature Request
Components: core
Affects Versions: AS 4.2.2.GA
Environment: JBoss-EAP-4.3-GA/JBoss-4.2.2
Reporter: Tyronne Wickramarathne
Assignee: Carlo de Wolf
Fix For: 1.0.0-Beta7
a mechanism is required to shut the connections down across all the MDB instances of the
same kind, when one instance caught up with a RuntimeException. ideally, we should be able
to configure a retry value. which enables the MDB instances to retry a specified number of
times before shutting down the connections as described and removing all the MDB instances
from the pool.
importantly, we should be able to restart this service via JMX console. if this
RuntimeException is triggered by a corrupted message, it should get moved to the DLQ
unless we specify a unique Queue to move such messages.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: