[
https://jira.jboss.org/jira/browse/JBMESSAGING-1296?page=com.atlassian.ji...
]
Andy Taylor commented on JBMESSAGING-1296:
------------------------------------------
This is how bisocket works. The client connects to the server on the main port and
notifies the server which port it has openened on the client side. The server then opens a
second connection back to the client on this port. The port chosen by the client is random
so if the client is behind a firewall this may fail. The secondary connect port is so you
can configure which port the client opens. Since Mina and netty only ever open a
connection from client to server this is not a problem.
Client connect port should be configurable
------------------------------------------
Key: JBMESSAGING-1296
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1296
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assignee: Andy Taylor
Fix For: 2.0.0 Beta
The client TCP connect port should be configurable in the JBM config, so it can work
behind firewalls where the port needs to be specified
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira