NameAlreadyBoundException in JBoss5.0.0Beta1

[javidjamae]

I'm trying to bring up a vertical cluster (Jboss 5.0.0Beta1) using virtual IPs on a Windows XP box. I've created two copies of the all configuration called node1 and node2. I start them in different console windows as follows:

./run.sh -b 192.168.1.140 -c node1
./run.sh -b 192.168.1.141 -c node2

I can bring up the first node, but when I try to bring up the second node, I get the following exception. I'm guessing that this is a bug???

19:12:28,656 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
19:12:28,828 INFO [StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-cons
ole] has already been started
19:12:29,109 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.1.140: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)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
 at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
 at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46
)
 at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:5
1)
 at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
 at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198)
 at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
 at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429)
 at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538)
 at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472)
 at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320)
 at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190)
 at org.jboss.system.ServiceController.doChange(ServiceController.java:656)
 at org.jboss.system.ServiceController.start(ServiceController.java:431)
 at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:124)
 at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:85)
 at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:44)
 at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.ja
va:53)
 at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
 at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
 at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
 at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:451)
 at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
 at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
 at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
 at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
 at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
 at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
 at org.jboss.Main.boot(Main.java:210)
 at org.jboss.Main$1.run(Main.java:508)
 at java.lang.Thread.run(Thread.java:595)
Caused by: javax.naming.NameAlreadyBoundException: jmxconnector [Root exception is java.rmi.AlreadyBoundException: jmxco
nnector]
 at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:118)
 at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
 at javax.naming.InitialContext.bind(InitialContext.java:359)
 at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
 at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
 ... 42 more
Caused by: java.rmi.AlreadyBoundException: jmxconnector
 at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:123)
 at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
 at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375)
 at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
 at sun.rmi.transport.Transport$1.run(Transport.java:153)
 at java.security.AccessController.doPrivileged(Native Method)
 at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
 at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
 at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
 at java.lang.Thread.run(Thread.java:595)
 at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
 at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
 at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
 at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
 at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
 ... 46 more
19:12:29,187 INFO [TomcatDeployment] deploy, ctxPath=/juddi, warUrl=.../deploy/juddi-service.sar/juddiws.war/

[javidjamae]

I forgot to mention that I've started the nodes in different orders, and it is always the second node that throws this exception.

[hmesha]

You must use binding manager to start more than one instance on the same machine: http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfiguringMultipleJBossInstancesOnOneMachine

[javidjamae]

No you don't. If you read the #1 option under the link that you sent me, it tells you how to do it without the ServiceBindingManager.

You can start multiple nodes so long as you bind them to different network addresses running on the same machine. This is what I did using the -b flag as I mentioned above. When you provide the -b flag, the instance that you start will bind and listen only on the IP address that you specify, so there are no port conflicts.

You can do this on a multi-homed box or use virtual IPs (the way that I'm doing it). To use virtual IPs in Windows, you have to go to the TCP/IP configuration for your network connection and add a static IP address then add additional IP addresses using the advanced settings. In unix, you can use ifconfig.

I find this to be a much easier way to run multiple nodes on the same machine than running the service binding manager.

[brian.stansberry]

It looks like JMXConnectorServer is not respecting the -b value. Can you open a JIRA against 5.0.0.Beta1 (if there isn't one already)?

[javidjamae]

Thanks Brian.

http://jira.jboss.com/jira/browse/JBAS-3885

[dimitris]

Actually, the problem is that the RMI registry that is created to store the remote object reference for the JMXConnectorServer, binds to all interfaces by default.

Then the same registry is seen by both servers, and the second registration fails, because the same name is used.

I believe I can fix it.