[jboss-jira] [JBoss JIRA] Assigned: (AS7-921) Booting AS7 on a system without any network connection throws up an error from ModClusterService

Booting AS7 on a system without any network connection throws up an error from ModClusterService ------------------------------------------------------------------------------------------------ Key: AS7-921 URL: https://issues.jboss.org/browse/AS7-921 Project: Application Server 7 Issue Type: Bug Environment: AS7 upstream (dated May 30 2011) Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 7.1.0.Alpha1 Starting AS7 (upstream) on a system which doesn't have any network connection throws up the following error during startup: {code} 15:38:22,766 ERROR [org.jboss.modcluster.ModClusterService] (MSC service thread 1-1) Error starting advertise listener: java.net.SocketException: No such device at java.net.PlainDatagramSocketImpl.join(Native Method) [:1.6.0_21] at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:172) [:1.6.0_21] at java.net.MulticastSocket.joinGroup(MulticastSocket.java:277) [:1.6.0_21] at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.init(AdvertiseListenerImpl.java:181) at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.start(AdvertiseListenerImpl.java:193) at org.jboss.modcluster.ModClusterService.init(ModClusterService.java:174) at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.init(CatalinaEventHandlerAdapter.java:335) at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.start(CatalinaEventHandlerAdapter.java:115) at org.jboss.as.modcluster.ModClusterService.start(ModClusterService.java:188) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] {code} Note that the server startup continues and starts up fine even with this error.