I don't know if this is relevant, but I just noticed I had a unit test that was creating an InvokerLocator with port == -1. It turns out that I was creating | socket://10.32.10.88:40404&serializationtype=java | instead of | socket://10.32.10.88:40404/?serializationtype=java | Later on, the parsing code in the InvokerLocator class turned the port into -1. Moral: check InvokerLocator. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255199#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...