MDB Failure Handling: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 17: Line 17:
=WildFly/HornetQ Behavior on RuntimeException=
=WildFly/HornetQ Behavior on RuntimeException=


==Message Delivery Occurs in a Transactional Context==
==Message Delivery Occurs in a Container-Managed Transactional Context==


What happens with the message?
What happens with the message?

Revision as of 14:08, 25 April 2017

Internal

Relevance

EAP 6.4.10

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

JSR 318 Enterprise JavaBeans Version 3.1 EJB Core Contract and Requirements, Section 5.4.18 "Dealing with Exceptions" mentions that MDBs should not 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.

WildFly/HornetQ Behavior on RuntimeException

Message Delivery Occurs in a Container-Managed Transactional Context

What happens with the message?

What happens with the transaction?

What happens with the MDB instance?

Message Delivery Occurs in a Non-Transactional Context

How to Indicate Failure in a Transactional Context

How to Indicate Failure in a Non-Transactional Context