2 Replies Latest reply on Jul 18, 2011 3:30 PM by Forman Loop

    Can't start JBoss bound to Loopback Adapter

    Forman Loop Newbie

      I am trying to create a vertical cluster for testing of clustering in general and mod-cluster specifically.  I have used a Microsoft Loopback Adapter, creating two IP addresses as suggested in "JBoss in Action" and in a local wiki article entitled "LoopAdapter."  I get the following error upon startup:


      08:56:46,973 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://]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: Exception creating connection to:; nested exception is:

              java.net.SocketException: Software caused connection abort: connect]

              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:131)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


      None of the "Caused by"s provide additional information, just "Exception creating connection."


      I'm running JBoss 5.1.0.GA on Windows XP Pro, Version 2002, Service Pack 3 on a Dell Optiplex 780 (Duo Core CPU, E8400@3GHz with 3.25GB of RAM).  My Java is reported by JBoss as "Java version: 1.5.0_09,Sun Microsystems Inc."  My start command is as follows:


      .\run.bat -c node1 -b -g Test_Partition -Djboss.service.binding.set=ports-01 -Djboss.messaging.ServerPeerID=1

      where node1 is a copy of "all."


      If I run this using the system's standard IP address (not the loopback), it runs fine.


      I've searched the web fairly extensively and find nothing that discusses this.  There were some that failed due to "already in use" issues, but they did not seem to apply.


      What am I missing?