You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by "Thomas McKiernan (JIRA)" <ji...@apache.org> on 2006/12/05 15:14:21 UTC
[jira] Created: (SANDESHA2-60) Axis QOS chain not tolerant of
duplicates
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Updated: (SANDESHA2-60) Axis QOS chain not tolerant of
duplicates
Posted by "Thomas McKiernan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-60?page=all ]
Thomas McKiernan updated SANDESHA2-60:
--------------------------------------
Attachment: OS_sendAcksIfNeeded.patch
> 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
> Attachments: OS_sendAcksIfNeeded.patch
>
>
> 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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Resolved: (SANDESHA2-60) Axis QOS chain not tolerant of
duplicates
Posted by "David Illsley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Illsley resolved SANDESHA2-60.
------------------------------------
Resolution: Fixed
Assignee: Andrew Gatford
Fixed in r482991
> Axis QOS chain not tolerant of duplicates
> -----------------------------------------
>
> Key: SANDESHA2-60
> URL: https://issues.apache.org/jira/browse/SANDESHA2-60
> Project: Sandesha2
> Issue Type: Bug
> Reporter: Thomas McKiernan
> Assignee: Andrew Gatford
> Attachments: OS_sendAcksIfNeeded.patch
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Updated: (SANDESHA2-60) Axis QOS chain not tolerant of
duplicates
Posted by "Thomas McKiernan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-60?page=all ]
Thomas McKiernan updated SANDESHA2-60:
--------------------------------------
Attachment: OS_sendAcksIfNeeded.patch
> 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
> Attachments: OS_sendAcksIfNeeded.patch
>
>
> 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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org