java.net.BindException: The socket name is already in use.

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 Oracle Community by 984556, 1 year ago
The socket name is already in use.
via Google Groups by cze...@visiospace.com, 2 years ago
Address already in use
via Netbeans Bugzilla by jleppanen, 1 year ago
via Google Groups by Randall Jameson, 2 years ago
The socket name is not available on this system.
via Coderanch by Charith De Silva, 11 months ago
via Google Groups by Evgeniy Kosinskiy, 2 months ago
Address already in use: Cannot bind > at java.net.PlainDatagramSocketImpl.bind0 (Native Method)
java.net.BindException: The socket name is already in use.
at java.net.PlainDatagramSocketImpl.bind(Native Method)
at java.net.DatagramSocket.create(DatagramSocket.java:188)
at java.net.DatagramSocket.(DatagramSocket.java:160)
at java.net.DatagramSocket.(DatagramSocket.java:132)
at oracle.apps.jtf.fm.engine.processor.RemoteMonitor.openSocket(RemoteMonitor.java:309)
at oracle.apps.jtf.fm.engine.processor.RemoteMonitor.run(RemoteMonitor.java:155)
at java.lang.Thread.run(Thread.java:513)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 2 years ago
Samebug visitor profile picture
Unknown user
Once, 2 years ago
Once, 11 months ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
1 more bugmates

Know the solutions? Share your knowledge to help other developers to debug faster.