Deployment Architecture

Splunk DB Connect: How to fix Java Bridge Server error "Unable to listen on localhost:17865: java.net.BindException: Address already in use"?

Ashish_Singla
Engager

This is the error I see in _internal index logs

main:FATAL:JavaBridgeServer - Unable to listen on localhost:17865: java.net.BindException: Address already in use
java.net.BindException: Address already in use
    at java.net.PlainSocketImpl.socketBind(Native Method)
    at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
    at java.net.ServerSocket.bind(ServerSocket.java:376)
    at java.net.ServerSocket.<init>(ServerSocket.java:237)
    at com.splunk.bridge.JavaBridgeServer.run(JavaBridgeServer.java:140)
    at java.lang.Thread.run(Thread.java:745)

Please suggest how it can be solved

1 Solution

MuS
SplunkTrust
SplunkTrust

Hi Ashish_Singla,

the port 17865 is already taken by another process. Change it in the java.conf http://docs.splunk.com/Documentation/DBX/1.1.6/DeployDBX/javaspec inside the DBX app.
It should be located at $SPLUNK_HOME/etc/apps/dbx/local/

cheers, MuS

View solution in original post

MuS
SplunkTrust
SplunkTrust

Hi Ashish_Singla,

the port 17865 is already taken by another process. Change it in the java.conf http://docs.splunk.com/Documentation/DBX/1.1.6/DeployDBX/javaspec inside the DBX app.
It should be located at $SPLUNK_HOME/etc/apps/dbx/local/

cheers, MuS

shekhar_mathur
New Member

Thanks,
The problem is resolved by specifying a new port for java bridge.

0 Karma
Get Updates on the Splunk Community!

Build Scalable Security While Moving to Cloud - Guide From Clayton Homes

 Clayton Homes faced the increased challenge of strengthening their security posture as they went through ...

Mission Control | Explore the latest release of Splunk Mission Control (2.3)

We’re happy to announce the release of Mission Control 2.3 which includes several new and exciting features ...

Cloud Platform | Migrating your Splunk Cloud deployment to Python 3.7

Python 2.7, the last release of Python 2, reached End of Life back on January 1, 2020. As part of our larger ...