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 osdir.com by Unknown author, 1 year ago
problem creating sockets (bind_addr=/160.61.106.230, mcast_addr=228.8.8.8:45566)
via nabble.com by Unknown author, 2 years ago
problem creating sockets > (bind_addr=/172.31.1.21, mcast_addr=ff0e:0:0:0:0:8:8:8:45588)
via Coderanch by bren jas, 1 year ago
problem creating sockets (bind_addr=/192.168.1.86, mcast_addr=null)
via shekhargulati.com by Unknown author, 2 years ago
problem creating sockets (bind_addr=shekhar/127.0.1.1, mcast_addr=228.10.10.10:45588)
via shekhargulati.com by Unknown author, 1 year ago
problem creating sockets (bind_addr=shekhar/127.0.1.1, mcast_addr=228.10.10.10:45588)
via JIRA by Alexey V. Zavizionov, 1 year ago
problem creating sockets (bind_addr=/fe80:0:0:0:250:56ff:fec0:8%3, mcast_addr=null)
java.lang.Exception: problem creating sockets (bind_addr=/160.61.106.230, mcast_addr=228.8.8.8:45566)	at org.jgroups.protocols.UDP.start(UDP.java:372)	at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:571)