Interesting problem. That InvokerLocator, "bisocket://uc_0183_0181/?JBM_clientMaxPoolSize ...", should have a port following the host. The way JBossMessaging works is, you download a connection factory, and the connection factory carries with it the InvokerLocator, which suggests that something is going wrong when JBossMessaging starts up on the server. Look for suspicious complaints in the server.log. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4253690#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...