Axis QOS chain not tolerant of duplicates
-----------------------------------------
Key: SANDESHA2-60
URL: http://issues.apache.org/jira/browse/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(OutInAxisOperation.java:69)
at
org.apache.axis2.context.OperationContext.addMessageContext(OperationContext.java:197)
at
org.apache.axis2.engine.AddressingBasedDispatcher.invoke(AddressingBasedDispatcher.java:124)
at org.apache.axis2.engine.Phase.invoke(Phase.java:382)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:245)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:164)
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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
