Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-4485

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • JBossAS-5.0.0.Beta3
    • JBossAS-5.0.0.Beta2
    • JMX
    • None

      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@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.

              dandread1@redhat.com Dimitrios Andreadis
              rhn-support-hbraun Heiko Braun
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: