4 Replies Latest reply on Jun 7, 2010 12:00 PM by Kobi Ianko

    4.0.5 to 4.2.1 hostname problem with port 4446?

    Frank Morton Newbie

      Jboss 4.2.1 (do not see this problem with 4.0.5)
      linux redhat enterprise/intel system
      java 1.5.0_12

      One instance of jboss inside firewall. IP address of system is 10.0.0.46. Valid external routeable address also
      assigned to the server. Start system including options:

      -Djava.rmi.server.useLocalHostname=true -Djava.rmi.server.hostname=ACTUALHOSTNAMEHERE

      Outside the firewall is another instance of jboss. Attach to inside system using:

      java.naming.provider.url=ACTUALHOSTNAMEHERE:1099

      Starting jboss using "-b 0.0.0.0".

      However, with 4.2.1, the external server is unable to attach to the server inside the firewall.

      Have seen this message from the external server:

      org.jboss.remoting.CannotConnectException: Can not get connection to
      server. Problem establishing socket connection for InvokerLocator
      [socket://10.0.0.46:4446/?dataType=invocation&enableTcpNoDelay=true&
      marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller&
      socketTimeout=600000&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller]

      Note that it is referring to the non-routeable address of the internal server (10.0.0.46) rather than the valid external ip address.

      So, I suspect there is some configuration file somewhere that determines where it grabs the hostname from,
      though I'd like to also hear other comments.

      Anyone know how to resolve this?