[
https://issues.jboss.org/browse/JBESB-3620?page=com.atlassian.jira.plugin...
]
Ryan LaMothe updated JBESB-3620:
--------------------------------
Description:
We are trying to handle faults in our asynchronous workflows (one way) and are properly
setting the faultTo address to a LocalEPR for further processing. When the LocalEPR is
called on a fault, the message that we receive contains only the fault and none of the
body or any other payload. Unfortunately, that is not enough information to process the
message further, alert the caller, etc.
The bug appears to be in the org.jboss.soa.esb.listeners.message.errors.Factory class
where the message payload is not being copied from the incoming message to the fault
message (see forum thread).
was:
We are trying to handle faults in our asynchronous workflows (one way) and are properly
setting the faultTo address to a LocalEPR for further processing. When the LocalEPR is
called on a fault, the message that we receive contains only the fault and none of the
body or any other payload. Unfortunately, that is not enough information to process the
message further, alert the caller, etc.
The bug appears to be in the org.jboss.soa.esb.listeners.message.errors.Factory class
where the message payload is not being copied from the incoming message to the faulty
message (see forum thread).
Forum Reference:
http://community.jboss.org/message/506312 (was:
http://community.jboss.org/message/506312)
FaultTo does not copy message payload to fault message
------------------------------------------------------
Key: JBESB-3620
URL:
https://issues.jboss.org/browse/JBESB-3620
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.9, 4.9 CP1
Environment: Mac OS X, RHEL 5, Windows 7, MySQL 5.x
Reporter: Ryan LaMothe
We are trying to handle faults in our asynchronous workflows (one way) and are properly
setting the faultTo address to a LocalEPR for further processing. When the LocalEPR is
called on a fault, the message that we receive contains only the fault and none of the
body or any other payload. Unfortunately, that is not enough information to process the
message further, alert the caller, etc.
The bug appears to be in the org.jboss.soa.esb.listeners.message.errors.Factory class
where the message payload is not being copied from the incoming message to the fault
message (see forum thread).
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira