Re: [jboss-dev] Binding the JMXConnector on a multihomed machine

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 0.0.0.0: (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) [tdiesler@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. Could this be an issue with JDK 5 JMX implementation? /Heiko _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development