[ https://jira.jboss.org/browse/ISPN-502?page=com.atlassian.jira.plugin.sys... ] Manik Surtani commented on ISPN-502: ------------------------------------ What exactly am I looking for here? Do you have a simple unit test that exhibits this behaviour? Is there a forum thread or something that explains this better? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-502?page=com.atlassian.jira.plugin.sys... ] Manik Surtani commented on ISPN-502: ------------------------------------ Cannot seem to reproduce. Here is a simple test: http://pastie.org/1028088 And this does not block, at all. Excerpts from my log file running this test: http://pastie.org/1028090 As you can see, the JGroupsTransport returns as soon as this RPC call is placed on the wire. The receiving end would have blocked before responding to the RPC since the lock on the key in question is held. To prove this, attempt the same test above with synchronous replication and you will see it block. The codepaths for sync and async are identical with the exception of the flags passed to JGroups when sending messages (and also skipping parsing responses as an optimisation for async). Perhaps the problem here has to do with JGroups' FC protocol (flow control) and senders running out of "credits" and hence blocking until other calls come in? See FC in JGroups' docs for more details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/ISPN-502?page=com.atlassian.jira.plugin.sys... ] Manik Surtani updated ISPN-502: ------------------------------- Fix Version/s: (was: 4.1.0.CR1) Affects Version/s: 4.1.0.BETA2 (was: 4.1.0.BETA1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira