[ http://issues.apache.org/jira/browse/SANDESHA2-32?page=all ]
Matt Lovett updated SANDESHA2-32:
---------------------------------
Attachment: inOrder.patch
Here's a patch that addresses this issue, and cleans up the build at the same
time. We needed to update the repository location in project.properties, and
the Axis2 handler API now requires us to return a flag to control further
processing. This patch uses that capability to remove the timing window that
Tom found.
Thanks
Matt
> Timing window with InOrder sequences
> ------------------------------------
>
> Key: SANDESHA2-32
> URL: http://issues.apache.org/jira/browse/SANDESHA2-32
> Project: Apache Sandesha2
> Issue Type: Bug
> Reporter: Thomas McKiernan
> Attachments: inOrder.patch
>
>
> When a sequence is InOrder, a msgCtx will be delivered using the
> InvokerWorker.
> This will unpause the msg and resume the send such that the app will be
> invoked with the msg.
> However, it is possible that the original recieving thread will not have
> completed at that point.
> Therefore the msg will be unpaused before this thread has finished.
> The result is the msg gets "invoked" twice and this causes problems for us at
> the JAXWS layer.
--
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]
