2 Replies Latest reply on Dec 3, 2004 1:46 PM by Tyler Black

    MulticastDector error during Detection of

    Tyler Black Newbie

      Recently upgraded to JBoss 4.0, working in a development environment with other machines on the LAN running their own JBoss application servers. On startup, we are getting:

      ERROR [MulticastDetector] Error during detection of: Detection [identity:JBOSS Identity [address: *address of individual JBOSS identity*...
      RuntimeOperationsException: null Cause: java.lang.IllegalArgumentException: null object name
       at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:495)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:636)
       at org.jboss.remoting.detection.AbstractDetector.detect(AbstractDetector.java:327)
       at org.jboss.remoting.detection.multicast.MulticastDetector.listen(MulticastDetector.java:212)
       at org.jboss.remoting.detection.multicast.MulticastDetector.access$100(MulticastDetector.java:32)
       at org.jboss.remoting.detection.multicast.MulticastDetector$Listener.run(MulticastDetector.java:240)
      Caused by: java.lang.IllegalArgumentException: null object name
       ... 6 more

      There must be a way to have our individual servers not detect each other and throw this error. I thought we might be able to change the mcast_port attribute of an MBean responsible for MulticastDetector, but I cannot find where this would be.

      Any advice on how to get this working? It doesn't cause problems in development, but I want to get a handle on this before we upgrade our production servers, which are in a somewhat complex multi-clustered topology.