Hi, JBoss AS: 4.2.2.GA JBM: 1.4.0.SP3 Remoting: 2.2.2.SP7-brew We are planning to use Http Transport instead of Bisocket Transport in JBoss Messaging; this is because we have an external load balancer which would balance the load across all the messaging instances (We have 5 JBoss Server running in 5 Physical Machines and one JBoss instance in each Server and there are many senders that would be sending messages and the load balancer would spread the load across the queues in a round robin fashion). Now we are unable to use bisocket transport because it opens a second port 4457 and keeps it open and our load balncer is configured to use 1099 and because the second port is always open, the load balancer is unable to do its work. Basically, when the load balancer gets the very first message, it chooses a instance to which it sends the message and then when the second message comes, it HAS to choose the next instance, BUT, that doesnt happen since the bisocket transport has a second port that is always open, the load balancer chooses the first machine to send the other messages that comes. Is there any way that we can stop the opening of the second port that is being opened by the Bisocket transport? BTW, I have read that bisocket transport is useful in place where the server is behind a firewall and this server opens the call back port (the second port 4457, here) so that clients can use that. Our Server is not behind a firewall and so we do not want the call back port. Thanks, Ebe View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160691#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...