There is a whole lot of posts around here saying the solution for "Failed to 
start AutomaticDiscovery" is to add "--host=ip-address" to the run.sh command 
line. Or else we get the dreaded:

INFO  [HANamingService] Listening on /0.0.0.0:1100
  | WARN  [HANamingService] Failed to start AutomaticDiscovery
  | java.net.SocketException: bad argument for IP_MULTICAST_IF: address not 
bound to any interface

However, if we do this, then other JBoss protocols too get bound to that 
interface. E.g., 127.0.0.1:8080 will no longer respond -- you now need to use 
the correct ip.

This causes trouble for us because we use various resources in EJB-code which 
are retrieved using "localhost:8080".

Question: Did anyone else experience this, and how did you solve it? 

Is it possible to detect the particular ip-address in code? (Or do we have to 
provide it explicitly through a System property?)


View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864675#3864675

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864675


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to