[jboss-remoting-issues] [JBoss JIRA] (JBREM-1322) Cannot set up serverBindAddress for secondarySocket in bisocket transport

Igor Kostromin (JIRA) jira-events at lists.jboss.org
Wed Jul 17 05:19:26 EDT 2013


Igor Kostromin created JBREM-1322:
-------------------------------------

             Summary: Cannot set up serverBindAddress for secondarySocket in bisocket transport
                 Key: JBREM-1322
                 URL: https://issues.jboss.org/browse/JBREM-1322
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: transport
    Affects Versions: 2.5.4.SP4
            Reporter: Igor Kostromin


Using IS_CALLBACK_SERVER = true.

In BisocketServerInvoker.java:355

String host = newLocator.getHost();
int port = newLocator.getPort();

It retrieves host from server, but if you want to use original client invoker host, you cannot do this (it is necessary if server is behind translating firewall). If you want to do this, you have to patch this code manually to

String host = clientInvoker.getLocator().getHost();
int port = newLocator.getPort();

and rebuild jboss-remoting project.

For ports there are settings SECONDARY_BIND_PORT, SECONDARY_CONNECT_PORT allowing to set up them as you want. For address there is no one to do this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-remoting-issues mailing list