Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Terracotta by the_god, 1 year ago
bad argument for IP_MULTICAST_IF: address not bound to any interface
via java.net by Unknown author, 2 years ago
bad argument for IP_MULTICAST_IF: address not bound to any interface
via sourceforge.net by Unknown author, 2 years ago
bad argument for IP_MULTICAST_IF: address not bound to any interface
via osdir.com by Unknown author, 1 year ago
via hivmr.com by Unknown author, 2 years ago
The socket name is not available on this system.
via Oracle Community by 696018, 2 years ago
The socket name is not available on this system.
java.net.SocketException: bad argument for IP_MULTICAST_IF: address not bound to any interface at java.net.PlainDatagramSocketImpl.socketSetOption(Native Method) at java.net.PlainDatagramSocketImpl.setOption(PlainDatagramSocketImpl.java:398) at java.net.MulticastSocket.setInterface(MulticastSocket.java:421) at net.sf.ehcache.distribution.MulticastKeepaliveHeartbeatReceiver.init(MulticastKeepaliveHeartbeatReceiver.java:85) at net.sf.ehcache.distribution.MulticastRMICacheManagerPeerProvider.init(MulticastRMICacheManagerPeerProvider.java:95) at net.sf.ehcache.CacheManager.init(CacheManager.java:306) at net.sf.ehcache.CacheManager.<init>(CacheManager.java:208) at net.sf.ehcache.distribution.RemoteDebugger.<init>(RemoteDebugger.java:75) at net.sf.ehcache.distribution.RemoteDebugger.main(RemoteDebugger.java:196)