Deployment Architecture

Splunk DB Connect V1 Database connection release

amahoski
Explorer

We are using Splunk DBConnect V1 and would like to know why a DBconnection stays open "sleeping" after disabling the connection within DBConnect. The only way that we have truly killed the connection is stopping Splunk.

Is there a way to do this without needing to stop the running splunk instance?

0 Karma
1 Solution

pmdba
Builder

Disabling the connection probably just prevents Splunk from opening new connections. I suspect that it won't disconnect existing ones. Check the java.conf file for connection pooling settings; consider setting pool.maxIdle=0 to let the connection pool cleanup all idle sessions. You should also have your database configured to time-out idle sessions and clean it up that way.

View solution in original post

pmdba
Builder

Disabling the connection probably just prevents Splunk from opening new connections. I suspect that it won't disconnect existing ones. Check the java.conf file for connection pooling settings; consider setting pool.maxIdle=0 to let the connection pool cleanup all idle sessions. You should also have your database configured to time-out idle sessions and clean it up that way.

Get Updates on the Splunk Community!

Feel the Splunk Love: Real Stories from Real Customers

Hello Splunk Community,    What’s the best part of hearing how our customers use Splunk? Easy: the positive ...

Data Management Digest – November 2025

  Welcome to the inaugural edition of Data Management Digest! As your trusted partner in data innovation, the ...

Splunk Mobile: Your Brand-New Home Screen

Meet Your New Mobile Hub  Hello Splunk Community!  Staying connected to your data—no matter where you are—is ...