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 "Andrew Gatford (JIRA)" <ji...@apache.org> on 2006/10/13 13:14:36 UTC
[jira] Created: (SANDESHA2-34) Service invoked multiple times when
using the Inorder and EXACTLY_ONCEQos
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
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Resolved: (SANDESHA2-34) Service invoked multiple times when
using the Inorder and EXACTLY_ONCEQos
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-34?page=all ]
Matt Lovett resolved SANDESHA2-34.
----------------------------------
Resolution: Fixed
> 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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Commented: (SANDESHA2-34) Service invoked multiple times
when using the Inorder and EXACTLY_ONCEQos
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-34?page=comments#action_12443045 ]
Chamikara Jayalath commented on SANDESHA2-34:
---------------------------------------------
Hi Andrew,
Applied that patch. Sorry i missed it last time :(
Chamikara
> 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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Updated: (SANDESHA2-34) Service invoked multiple times when
using the Inorder and EXACTLY_ONCEQos
Posted by "Andrew Gatford (JIRA)" <ji...@apache.org>.
[ 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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Commented: (SANDESHA2-34) Service invoked multiple times
when using the Inorder and EXACTLY_ONCEQos
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-34?page=comments#action_12443045 ]
Chamikara Jayalath commented on SANDESHA2-34:
---------------------------------------------
Hi Andrew,
Applied that patch. Sorry i missed it last time :(
Chamikara
> 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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Updated: (SANDESHA2-34) Service invoked multiple times when
using the Inorder and EXACTLY_ONCEQos
Posted by "Andrew Gatford (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-34?page=all ]
Andrew Gatford updated SANDESHA2-34:
------------------------------------
Attachment: InvokeMultipleTimes.patch
Patch to stop multiple invokes
> 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
>
>
> 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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Updated: (SANDESHA2-34) Service invoked multiple times when
using the Inorder and EXACTLY_ONCEQos
Posted by "Andrew Gatford (JIRA)" <ji...@apache.org>.
[ 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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Resolved: (SANDESHA2-34) Service invoked multiple times when
using the Inorder and EXACTLY_ONCEQos
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-34?page=all ]
Matt Lovett resolved SANDESHA2-34.
----------------------------------
Resolution: Fixed
> 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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Updated: (SANDESHA2-34) Service invoked multiple times when
using the Inorder and EXACTLY_ONCEQos
Posted by "Andrew Gatford (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-34?page=all ]
Andrew Gatford updated SANDESHA2-34:
------------------------------------
Attachment: InvokeMultipleTimes.patch
Patch to stop multiple invokes
> 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
>
>
> 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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org