[ https://jira.jboss.org/jira/browse/JBAS-7102?page=com.atlassian.jira.plug... ] Brian Stansberry updated JBAS-7102: ----------------------------------- Priority: Major (was: Critical) As noted on the forum thread, this occurred in an environment that was experiencing major multicast packet losses. In this particular case wasn't due to network buffer settings; rather seemed to be an OS virtualization problem. So not really a FarmService problem per se, so reducing from Critical to Major. I'm leaving this open to see if I can find a way to make the service be a bit more responsive in these situations. What happens is it sends file chunks via HAPartition RPC, then waits for a response. The last chunk gets dropped by JGroups so there is no response. So FarmService waits 60 secs (default HAPartition RPC timeout) then sends the next chunk. The fact that responses weren't received is ignored. Possible improvement is to send the chunks via async RPCs. The RPCs return null, and non-responses are ignored, so what's the benefit of a synchronous RPC? Even w/ asynch RPCs JGroups ensures lossless, ordered message receipt, and that's all that is really needed for these file chunks. The synchronous RPCs can be reserved for the final commit messages. Effect of the improvement is there won't be long pauses in the transmission of file chunks. Lossy networks will still be slow, but should be better than what users reported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira