[
https://jira.jboss.org/jira/browse/JBESB-2227?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBESB-2227:
-------------------------------------
Kev, can you clarify exactly what you've seen here.
I see one issue re fault delivery and have fixed it locally. It's where you set the
faultTo using a LogicalEPR and there's an error in the action pipeline on an async
delivery.
The issue is with the ServiceInvoker while delivering the fault message to the FaultTo
address (using a LogicalEPR). The ServiceInvoker.EPRInvoker class returns the original
message on a successful async delivery (returns the actual response on a sync delivery).
Looks as though this return is used by the ServiceInvoker as an indication that the
delivery was successful (a bit of a dodgy way of doing that, but anyway...). Then, this
return value is being confused (by the post method) as meaning a replyMessage from a
successful sync call. The message gets checked and they see it's a fault message
(because it's the original), which raises an unexpected FaultMessageException.
Was this what you were seeing?
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