You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Paul Fremantle (JIRA)" <ji...@apache.org> on 2007/06/22 15:30:33 UTC
[jira] Created: (SANDESHA2-92) Sandesha2 closing inbound sequence
when it shouldn't
Sandesha2 closing inbound sequence when it shouldn't
----------------------------------------------------
Key: SANDESHA2-92
URL: https://issues.apache.org/jira/browse/SANDESHA2-92
Project: Sandesha2
Issue Type: Bug
Reporter: Paul Fremantle
Sandesha1.2
When I do the following:
setUseSeparateListener(true)
engageModule(sandesha2)
stub.startMyMethod(...., callback)
setProperty(Sandesha2LastMessage, true);
stub.startMyMethod(....., callback)
The second response fails because Sandesha is automatically terminating the inbound sequence when it terminates the outbound sequence. So by the time the second response comes in the Offered sequence is dead and I get an exception saying that the message references a terminated sequence.
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org