[ http://issues.apache.org/jira/browse/SANDESHA2-45?page=all ]
Matt Lovett resolved SANDESHA2-45.
----------------------------------
Resolution: Fixed
> Terminate messages are sent even if the sequence is already terminated and
> sent more than once
> ----------------------------------------------------------------------------------------------
>
> Key: SANDESHA2-45
> URL: http://issues.apache.org/jira/browse/SANDESHA2-45
> Project: Apache Sandesha2
> Issue Type: Bug
> Reporter: Andrew Gatford
> Attachments: terminate.patch
>
>
> Terminate messages are sent more then once. This is due to the fact that the
> suspend response is not returned to the SandeshaOutHandler.
> This means that both the thread that requested the terminate and the Sender
> thread will both send the terminate message.
> In addition to this when the sequence has already been terminated, then the
> terminate processor should return suspend for the message.
> Finally it is possible for a terminate sequence message to not have a
> sequence key set, but it can still find the sequenceId and the internal
> sequence id.
> In this case the Sender will fail with an exception indicating that the
> PropertyKey can't be found. This can be fixed by adding the sequence id and
> internal sequence id to the SenderBean for the terminate 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]
