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!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...