I recently upgraded to JBM 1.4.0.CR3/Remoting 2.2.2.SP1, and all appears to work fine. However, I noticed that if you accidently try to connect a client to the JBM server using an incorrect client remoting library, then all future client createConnection calls will hang (even with the correct client remoting libraries). The JBM server has to be restarted to correct the problem. Has anyone else seen this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088421#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...