I'm trying to get JBoss to bind to all addresses. I've tried both specifying and not specifying the jboss.bind.address option. Either way, when JBoss is starting up, it freezes for several minutes at the last line listed in the log snippet below. If I specify an address with the option it starts up without hesitation. Does anyone have any ideas as to why this is happening?
2007-03-15 14:14:45,786 INFO [Catalina] Server startup in 639 ms 2007-03-15 14:14:46,533 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/ 2007-03-15 14:14:47,541 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined 2007-03-15 14:14:49,135 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/ 2007-03-15 14:14:50,414 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp34358jbossws-context-exp.war/ 2007-03-15 14:14:51,615 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ 2007-03-15 14:14:52,652 INFO [STDOUT] classname is org.jboss.management.j2ee.LocalJBossServerDomain 2007-03-15 14:14:52,653 INFO [STDOUT] The attribute : servers is not found in jboss.management.local:j2eeType=J2EEDomain,name=Manager 2007-03-15 14:14:52,653 INFO [STDOUT] classname is org.jboss.management.j2ee.J2EEDomain
I have a feeling that one of your networks cards is bad, or disconnected, or something, in which case the app server is waiting for a network request to timeout before going on to the next address. I have no problems with getting the app server to connect to multiple addresses, both on Windows and Linux.