ws-sandesha-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas McKiernan (JIRA)" <>
Subject [jira] Created: (SANDESHA2-60) Axis QOS chain not tolerant of duplicates
Date Tue, 05 Dec 2006 14:14:21 GMT
Axis QOS chain not tolerant of duplicates

                 Key: SANDESHA2-60
             Project: Apache Sandesha2
          Issue Type: Bug
            Reporter: Thomas McKiernan

Because the SandeshaGlobalInHandler is set to run before the instanceDispatcher, it runs after
the addressing based dispatcher.
This means duplicate filtering happens after the addressing dispatcher, and the addressing
dispatcher is not tolerant of duplicates.
The following error msg is received:

[01/12/06 16:18:25:923 GMT] 0000002f AsyncInRespon E   org.apache.axis2.AxisFault: A message
was added that is not valid. However, the operation context was completed.
       at org.apache.axis2.description.OutInAxisOperation.addMessageContext(
       at org.apache.axis2.context.OperationContext.addMessageContext(
       at org.apache.axis2.engine.AddressingBasedDispatcher.invoke(
       at org.apache.axis2.engine.Phase.invoke(
       at org.apache.axis2.engine.AxisEngine.invoke(
       at org.apache.axis2.engine.AxisEngine.receive(

The fix is to make the inHandler run before the addressing based dispatcher. However, this
then causes problems in the sendAckIfNeeded code
due to the axisOperation code not being resolved anymore.
Luckily, that code can be refacotred only slightly to depend only on the axis service.
I will attach a patch to fix this.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message