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!

Enterprise Security (ES) Essentials 8.3 is Now GA — Smarter Detections, Faster ...

As of today, Enterprise Security (ES) Essentials 8.3 is now generally available, helping SOC teams simplify ...

AI for AppInspect

We’re excited to announce two new updates to AppInspect designed to save you time and make the app approval ...

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...