synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <>
Subject [jira] Created: (SYNAPSE-612) Stop I/O Exception handling for RM messages
Date Mon, 22 Feb 2010 17:52:28 GMT
Stop I/O Exception handling for RM messages

                 Key: SYNAPSE-612
             Project: Synapse
          Issue Type: Bug
            Reporter: Amila Chinthaka Suriarachchi

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:
For additional commands, e-mail:

View raw message