[jira] Assigned: (SYNAPSE-612) Stop I/O Exception handling for RM messages

["Ruwan Linton (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SYNAPSE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ruwan Linton reassigned SYNAPSE-612:
------------------------------------

    Assignee: Ruwan Linton

> 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
>            Assignee: Ruwan Linton
>         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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org