[
https://issues.apache.org/jira/browse/SANDESHA2-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576194#action_12576194
]
Hans G Knudsen commented on SANDESHA2-132:
------------------------------------------
Hi!
I just re-tested with a fresh checkout of Sandesha2 (rev 634671) + Axis2....
The SequenceAcknowledge is no longer sent as an extra message to the
LastMessage (response).
But it is still sent as the first response to a LastMessage (request) and
thereby violating "Server Processing Model - F" from [1].
After this the client resends/replays the LastMessage which is responded with a
LastMessage. After this the TerminateMessage should have been sent - but
instead a new LastMessage is sent which again is responded with a LastMessage.
The 'actions' of the message sequence looks like :
===> CreateSequence
<=== CreateSequenceResponse
===> PayloadRequest
<=== PayloadResponse
===> LastMessage
<=== SequenceAcknowledgement
===> LastMessage
<=== LastMessage
===> LastMessage
<=== LastMessage
/hans
[1] http://wso2.org/library/2792
> SequenceAcknowledgement is sent with LastMessage (Response) using replay model
> ------------------------------------------------------------------------------
>
> Key: SANDESHA2-132
> URL: https://issues.apache.org/jira/browse/SANDESHA2-132
> Project: Sandesha2
> Issue Type: Bug
> Environment: Axis2, Sandesha2 trunk
> Reporter: Hans G Knudsen
>
> Hi!
> I noticed that a SequenceAcknowledgement is sent back on the same
> http-backchannel as the LastMessage (response), when using the replay model.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
