I can't tell what's going on from that exception by itself. I would suggest turning on trace logging for both JBossMessaging and Remoting to see if there's anything suspicious happening. To turn on trace logging, add | <!-- Remoting --> | <category name="org.jboss.remoting"> | <priority value="TRACE"/> | </category> | | <!-- JBossMessaging --> | <category name="org.jboss.jms"> | <priority value="TRACE"/> | </category> | to your conf/jboss-log4j.xml file. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114840#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...