Hi, I am the "customer" that incoutered this issue with log4j and NFS. In our TEST Jboss cluster, we solved this by installing all our JBOSS AS into a local file system insteed of NFS. Since then, it never happed again. But just this morning, we had the same issue in our PRODUCTION environement. Meaning that all EJB calls inter-jboss where dreadfully slow. We solved it by restarting one of our Jboss that was somehow "stuck" ( but not by log4j that time!). The problem is this: when just one Jboss server is stuck, the whole Jgroup cluster is stuck. This issue is terrible for us, because we have a big heterogenous cluster with 20 applications (nodes) on it. So when this issue araises, all the application are not working. My question is this: if we switch to several homogenous cluster ( each application has it how small cluster (partition) of 2 to 4 nodes), will this leverage the effect of this issue ? Thanks in advance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125145#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...