[ http://issues.apache.org/jira/browse/SANDESHA2-34?page=all ]
Andrew Gatford updated SANDESHA2-34:
------------------------------------
Attachment: InvokeMultipleTimes.patch
Adding patch again based on the latest level
> Service invoked multiple times when using the Inorder and EXACTLY_ONCEQos
> -------------------------------------------------------------------------
>
> Key: SANDESHA2-34
> URL: http://issues.apache.org/jira/browse/SANDESHA2-34
> Project: Apache Sandesha2
> Issue Type: Bug
> Reporter: Andrew Gatford
> Priority: Critical
> Attachments: InvokeMultipleTimes.patch, InvokeMultipleTimes.patch
>
>
> There is a timing window inside the SandeshaGlobalInHandler where the
> duplicate checking is done.
> If 2 messages with the same sequence number arrive at similar times in the
> SandeshaGlobalInHandler, then it is possible for the duplicate checking to
> allow both messages to proceed to the
> ApplicationMessageProcessor.processInMessage.
> The timing window is between the SandeshaGlobalInHandler.dropIfDuplicate
> method and the ApplicationMessageProcessor.processInHandler which actually
> sets the message into the SERVER_COMPLETED_MESSAGES property. In this case,
> any messages doing the dropIfDuplicate check in the SandeshaGlobalInHandler
> will pass as they are not duplicates until the completed messages is updated.
> If this happens then the service will be invoked more than once with the
> same sequence message.
--
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]
