I'll explain the meaning of "secondaryBindPort" and "secondaryConnectPort", and maybe that will help.
The Remoting bisocket transport creates two ServerSockets on the server. The "primary" ServerSocket is used to create connections used for ordinary invocations, e.g., a request to create a JMS consumer, and the "secondary" ServerSocket is used to create "control" connections for internal Remoting messages. The port for the primary ServerSocket is configured by the "serverBindPort" parameter, and the port for the secondary ServerSocket is, by default, chosen randomly. The "secondaryBindPort" parameter can be used to assign a specific port to the secondary ServerSocket. Now, if there is a translating firewall between the client and server, the client should be given the value of the port that is translated to the actual binding port of the secondary ServerSocket. For example, your configuration will tell the secondary ServerSocket to bind to port 14000, and it will tell the client to connect to port 14001. It assumes that there is a firewall which will translate 14001 to 14000. Apparently, that's not happening. Hope that helps. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204136#4204136 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204136 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
