[ 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
