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
Legend

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
Legend

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!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...