[
https://issues.apache.org/jira/browse/SANDESHA2-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556570#action_12556570
]
Hans G Knudsen commented on SANDESHA2-134:
------------------------------------------
Forgot to mention...
The lookup does not occur on every request.
Only randomly.
/hans
> Client deadlocks and does not finish using Replay Model
> -------------------------------------------------------
>
> Key: SANDESHA2-134
> URL: https://issues.apache.org/jira/browse/SANDESHA2-134
> Project: Sandesha2
> Issue Type: Bug
> Environment: Axis2 + Sandesha2 trunk
> Reporter: Hans G Knudsen
>
> Hi!
> Trying to find a testcase for
> http://issues.apache.org/jira/browse/SANDESHA2-122
> I noted that sometimes the client does not finish even though the response is
> written back to the client.
> I have used the same test case as attached to
> http://issues.apache.org/jira/browse/SANDESHA2-122.
> The service has a 10 second sleep in the service call and the client has 5
> sec RetransmisssionInterval (no exp backoff)
> The RM Scenario looks like :
> --> CreateSequence
> <-- CreateSequenceResponse
> --> Payload request
> *** 10 sec sleep in service
> --> Payload Request (replay)
> *** service wakes up
> <-- Payload response
> <-- Payload response
> After this the client seems to die.
> - The response is not written to the client callback
> - The requstst is not replayed
> I cannot see which response comes first.
--
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]
