MDB Failure Handling: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * MDB =Overview= This article addresses failure handling in an MDB context. It was written while experimenting with EAP 6.4 and a Hornet...") |
|||
| Line 7: | Line 7: | ||
This article addresses failure handling in an MDB context. It was written while experimenting with EAP 6.4 and a HornetQ-based messaging subsystem. | This article addresses failure handling in an MDB context. It was written while experimenting with EAP 6.4 and a HornetQ-based messaging subsystem. | ||
=Specification= | =Failure Handling Specification= | ||
MDBs should not, in general, throw RuntimeExceptions. If a RuntimeExceptions occurs, the container will transition the MDB in the "does not exist" state. The message will not be acknowledged, and if messages arrive to the destination, the container can delegate the message to another MDB instance. | MDBs should not, in general, throw RuntimeExceptions. If a RuntimeExceptions occurs, the container will transition the MDB in the "does not exist" state. The message will not be acknowledged, and if messages arrive to the destination, the container can delegate the message to another MDB instance. | ||
Revision as of 13:34, 25 April 2017
Internal
Overview
This article addresses failure handling in an MDB context. It was written while experimenting with EAP 6.4 and a HornetQ-based messaging subsystem.
Failure Handling Specification
MDBs should not, in general, throw RuntimeExceptions. If a RuntimeExceptions occurs, the container will transition the MDB in the "does not exist" state. The message will not be acknowledged, and if messages arrive to the destination, the container can delegate the message to another MDB instance.