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/15 10:40:39 UTC
[jira] Created: (SANDESHA2-43) Enable client to force dispatch on
inbound sequence
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
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
[jira] Resolved: (SANDESHA2-43) Enable client to force dispatch on
inbound sequence
Posted by "Thomas McKiernan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas McKiernan resolved SANDESHA2-43.
---------------------------------------
Resolution: Fixed
> Enable client to force dispatch on inbound sequence
> ---------------------------------------------------
>
> Key: SANDESHA2-43
> URL: https://issues.apache.org/jira/browse/SANDESHA2-43
> Project: 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.
-
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
[jira] Commented: (SANDESHA2-43) Enable client to force dispatch on
inbound sequence
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-43?page=comments#action_12451653 ]
Chamikara Jayalath commented on SANDESHA2-43:
---------------------------------------------
Hi Thomas,
I'm running sun JDK 1.4 on linux. Please go ahead and apply the patch if it is passing for u. I'm stuck with some stuff due to 1.1 release :-( . Will try to find out why these are failing for me, as soon as I get those settled.
Chamikara
> 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
[jira] Updated: (SANDESHA2-43) Enable client to force dispatch on
inbound sequence
Posted by "Thomas McKiernan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-43?page=all ]
Thomas McKiernan updated SANDESHA2-43:
--------------------------------------
Attachment: patch_forceInvoke.txt
> 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
[jira] Commented: (SANDESHA2-43) Enable client to force dispatch on
inbound sequence
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-43?page=comments#action_12450957 ]
Chamikara Jayalath commented on SANDESHA2-43:
---------------------------------------------
Hi Tom,
The patch seems great. But when I tried to run the build with it I'm getting a OutOfMemoryError in 'ForceInboundDispatchTest'. will try to dig in bit more.
BTW I had to do two small changes to make the code compile with JDK 1.4
rangeMap.remove(above.lowerValue) -> rangeMap.remove(new Long (above.lowerValue))
rangeMap.put(above.lowerValue, above) -> rangeMap.put(new Long (above.lowerValue), above);
Chamikara
> 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
[jira] Commented: (SANDESHA2-43) Enable client to force dispatch on
inbound sequence
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-43?page=comments#action_12451653 ]
Chamikara Jayalath commented on SANDESHA2-43:
---------------------------------------------
Hi Thomas,
I'm running sun JDK 1.4 on linux. Please go ahead and apply the patch if it is passing for u. I'm stuck with some stuff due to 1.1 release :-( . Will try to find out why these are failing for me, as soon as I get those settled.
Chamikara
> 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
[jira] Updated: (SANDESHA2-43) Enable client to force dispatch on
inbound sequence
Posted by "Thomas McKiernan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-43?page=all ]
Thomas McKiernan updated SANDESHA2-43:
--------------------------------------
Attachment: patch_forceInvoke.txt
> 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
[jira] Commented: (SANDESHA2-43) Enable client to force dispatch on
inbound sequence
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-43?page=comments#action_12450957 ]
Chamikara Jayalath commented on SANDESHA2-43:
---------------------------------------------
Hi Tom,
The patch seems great. But when I tried to run the build with it I'm getting a OutOfMemoryError in 'ForceInboundDispatchTest'. will try to dig in bit more.
BTW I had to do two small changes to make the code compile with JDK 1.4
rangeMap.remove(above.lowerValue) -> rangeMap.remove(new Long (above.lowerValue))
rangeMap.put(above.lowerValue, above) -> rangeMap.put(new Long (above.lowerValue), above);
Chamikara
> 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
[jira] Commented: (SANDESHA2-43) Enable client to force dispatch on
inbound sequence
Posted by "Thomas McKiernan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-43?page=comments#action_12451280 ]
Thomas McKiernan commented on SANDESHA2-43:
-------------------------------------------
Hi Chamikara,
Hmm, the test seems to pass cleanly in my environment.
Have you got any further with these errors? If not, please can you send me details as I cannot seem to reproduce. What environment are you running in? Do you get any other failures in the bucket?
Many thanks,
Thomas
> 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
[jira] Commented: (SANDESHA2-43) Enable client to force dispatch on
inbound sequence
Posted by "Thomas McKiernan (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (SANDESHA2-43) Enable client to force dispatch on
inbound sequence
Posted by "Thomas McKiernan (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (SANDESHA2-43) Enable client to force dispatch on
inbound sequence
Posted by "Thomas McKiernan (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/SANDESHA2-43?page=comments#action_12451280 ]
Thomas McKiernan commented on SANDESHA2-43:
-------------------------------------------
Hi Chamikara,
Hmm, the test seems to pass cleanly in my environment.
Have you got any further with these errors? If not, please can you send me details as I cannot seem to reproduce. What environment are you running in? Do you get any other failures in the bucket?
Many thanks,
Thomas
> 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