[ http://jira.jboss.com/jira/browse/JGRP-774?page=comments#action_12415504 ] Bela Ban commented on JGRP-774: ------------------------------- Another observation: it works with STATE_TRANSFER if we use the TCP transport ! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JGRP-774?page=comments#action_12415524 ] Bela Ban commented on JGRP-774: ------------------------------- Passes on 2.4 and 2.5, but fails on 2.6, so the regression must have happened in 2.6. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JGRP-774?page=comments#action_12415582 ] Bela Ban commented on JGRP-774: ------------------------------- Okay, the cause is this (A is the state provider, B the requester): - A gets the unicast GET-STATE request - This acquires a lock on the AckReceiverWindow for B - The GET-STATE request is passed up - The app provides the state and sends it back to B *in the same thread* - Since the state is large, FRAG2 breaks it into smaller fragments messages) - One of those messages gets blocked in FC.down() (above UNICAST), as we're out of credits - B sends new credits to A, but A will *not* receive them as those credits (as *OOB* message) have to pass through UNICAST first - However, UNICAST won't let the CREDIT message pass as the original GET-STATE request stilll holds the lock for B's AckReceiverWindow ! SOLUTION: - OOB requests should *never* have to acquire the lock on an AckreceiverWindow; we simply add the request to the AckReceiverWindow, pass up the message, and then return - This way, OOB messages will never block on other (unrelated) messages in UNICAST TODO: apply the same code changes to NAKACK (see sub-issue) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JGRP-774?page=comments#action_12415841 ] Bela Ban commented on JGRP-774: ------------------------------- Unit test for duplicate messages is DuplicateTest -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira