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 "Thomas McKiernan (JIRA)" <ji...@apache.org> on 2006/11/17 14:36:38 UTC
[jira] Commented: (SANDESHA2-43) Enable client to force dispatch on
inbound sequence
[ http://issues.apache.org/jira/browse/SANDESHA2-43?page=comments#action_12450740 ]
Thomas McKiernan commented on SANDESHA2-43:
-------------------------------------------
This patch does what is required. Please could people take a look and commit if they are happy
> Enable client to force dispatch on inbound sequence
> ---------------------------------------------------
>
> Key: SANDESHA2-43
> URL: http://issues.apache.org/jira/browse/SANDESHA2-43
> Project: Apache Sandesha2
> Issue Type: Improvement
> Reporter: Thomas McKiernan
> Priority: Minor
> Attachments: patch_forceInvoke.txt
>
>
> Currently, if an inbound message does not arrive (perhaps it has poisoned the sending client) it is possible to have messages on the inbound side waiting indefinately for the gap to be filled.
> We have a requirement for SadeshaClient to be able to force the out of order dispatch of inbound messages on an in order sequence. This way the user is given the choice to enable the sequence to make progress.
> This should pause the invoker, dispatch any outstanding messages and then resume the invoker.
--
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