[
https://issues.apache.org/jira/browse/SYNAPSE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi updated SYNAPSE-612:
-------------------------------------------------
Attachment: patch.txt
above patch checks for a property set by the Sandesha and omit the message if
it is set.
> Stop I/O Exception handling for RM messages
> -------------------------------------------
>
> Key: SYNAPSE-612
> URL: https://issues.apache.org/jira/browse/SYNAPSE-612
> Project: Synapse
> Issue Type: Bug
> Reporter: Amila Chinthaka Suriarachchi
> Attachments: patch.txt
>
>
> This problem occurs with sandesha and synapse.
> Lets take the scenario as in sample 101 where synapse end point reliably
> talks to axis2Server.
> if the axis2Server down initially this causes and I/O exception at the
> ClientHandler and which result in creating a FaultMessage context
> and send it through Axis2 Engine.
> However if RM is engaged I/O errors should not cause system Faults. Further
> above action completes the Mep of the opeationContext. Therefore it won't be
> able to get the correct response.
> if (responseMsgCtx == null && outMsgCtx.getOperationContext().isComplete()) {
> if (log.isDebugEnabled()) {
> log.debug("Error getting IN message context from the
> operation context. " +
> "Possibly an RM terminate sequence message");
> }
> }
> if the mep is completed Client worker does not set the responseMessageContext.
> To fix this issue synapse should not process the I/O errors when RM is
> engaged.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
