[jboss-jira] [JBoss JIRA] Created: (JBAS-4485) JMXConnector always binds to the loopback device, regardless of the actual bind address

[Heiko Braun (JIRA)]

JMXConnector always binds to the loopback device, regardless of the actual bind address
---------------------------------------------------------------------------------------

                 Key: JBAS-4485
                 URL: http://jira.jboss.com/jira/browse/JBAS-4485
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
         Environment: URL: https://svn.jboss.org/repos/jbossas/trunk
Repository Root: https://svn.jboss.org/repos/jbossas
Repository UUID: 84be2c1e-ba19-0410-b317-a758671a6fc1
Revision: 63502

java version "1.5.0_10"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode, sharing)

Linux jbws 2.6.20-1.2925.fc6 #1 SMP Sat Mar 10 19:15:16 EST 2007 i686 i686 i386 GNU/Linux

            Reporter: Heiko Braun


I am having trouble with a multihome setup.
Event though I am using dedicated bind addresses the JXMConnector fails
to start on the second instance. It looks to like as if the bind address
is just disregarded and instead binds to to the loopback device

(1) Instance A  (-b 192.168.0.101) started successfully
(2) Instance B (-b 192.168.0.102) logs:
17:41:37,489 ERROR [AbstractKernelController] Error installing to Start:
name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create
mode=Manual requiredState=Installed
java.io.IOException: Cannot bind to URL
[rmi://192.168.0.102:1090/jmxconnector]:
javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is
java.rmi.AlreadyBoundException: jmxconnector]
        at
javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
        at
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
        at
org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:110)


(3) [hbraun at jbws jboss-5.0.0.Beta3]$ netstat -ln | grep 1090
                
        tcp        0      0 0.0.0.0:1090  0.0.0.0:*  LISTEN     


The log is quiet misleading. It does actually bind to 0 0.0.0.0:1090.
As far as i can tell, it pulls the jdk 1.5 JMX implementation.  


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira