I forgot to mention that I've started the nodes in different orders, and it is
always the second node that throws this exception.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988708#3988708
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=p
You must use binding manager to start more than one instance on the same
machine:
http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfiguringMultipleJBossInstancesOnOneMachine
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988717#3988717
Reply to the post :
http:
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 menti
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)?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988943#3988943
Reply to the post :
http://www.jboss.com/index.html?module=b
Thanks Brian.
http://jira.jboss.com/jira/browse/JBAS-3885
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988953#3988953
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988953
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
