In previous versions of JBoss EAP it was found that the "fail" address-full-policy in HornetQ mostly dropped messages without sending an exception to the client.
This resulted in messages being dropped without an exception whenever an address was full.
This issue was resolved so that blocking sends always result in an exception on the client when the address is full and non-blocking sends will result in an exception on the client when additional credits are requested from the server.
+++ This bug was initially created as a clone of Bug #1088604 +++
Should be fixed by upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1064596 for DR2
Verified in EAP 6.3.0.ER7 / HornetQ 2.3.19.Final