[
https://jira.jboss.org/jira/browse/JBESB-2227?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2227:
-------------------------------------
It is simply sending a fault message, using deliverAsync. ServiceInvoker treats the reply
from async as a response and then throws a FaultMessageException, this gets translated in
deliverAsync to a MessageDeliverException.
This is nothing to do with the pipeline, although that would certainly see it, as this
would happen with any client sending a fault through deliverAsync.
The use of the response to indicate a successful delivery is, as you say, very dodgy
coding.
Asynchronous sending of a fault message causes the fault to be
raised
---------------------------------------------------------------------
Key: JBESB-2227
URL:
https://jira.jboss.org/jira/browse/JBESB-2227
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.4, 4.4 CP1
Reporter: Kevin Conner
Assignee: Tom Fennelly
Fix For: 4.5, 4.4 CP2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira