I'm having a bit of an issue here.. We have setup 3 servers: DMZ = Jboss Messaging 1.4.0 GA server in a DMZ zone. CORE = Jboss Messaging 1.4.0 GA server in a internal zone. APP = Jboss AS 4.2.0 server in same zone as CORE. APP is setup with 2 remote JMS providers, one for CORE and one for DMZ. Connection flow: DMZ <- APP -> CORE Between the DMZ and the APP server there is a firewall. In the DMZ server log we can see constant ERROR messages of type "received new control socket for unrecognized listenerId: xxx". I suspect the reason for this is that the Client opens up random callback ports but the server is not allowed through the firewall. Normally one would set up the client to use a specific callback port by supplying the VM arg jboss.messaging.callback.bind.port=. In this case the APP server acts as a clinet for two servers and specifying the jboss.messaging.callback.bind.port on the VM level results in one of the providers failing with a "The invoker for locator (....) is already in use by another Connector" exception. The Invoker subsystem seems to be configurable through the remoting-*-service.xml on the Server side, but on the Client side it is hardcoded in JMSRemotingConnection.start to use the static final variable ServerPeer.REMOTING_JMS_SUBSYSTEM. The use of the VM variable jboss.messaging.callback.bind.port is also hardcoded in the JMSRemotingConnection and there seem to be no way of adding your own metadata to a Client instance. Maybe one should be able to supply this kinda information by setting properties on the JMSProviderAdaptor or something similar. -aslak- View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100270#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...