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!

Updated Team Landing Page in Splunk Observability

We’re making some changes to the team landing page in Splunk Observability, based on your feedback. The ...

New! Splunk Observability Search Enhancements for Splunk APM Services/Traces and ...

Regardless of where you are in Splunk Observability, you can search for relevant APM targets including service ...

Webinar Recap | Revolutionizing IT Operations: The Transformative Power of AI and ML ...

The Transformative Power of AI and ML in Enhancing Observability   In the realm of IT operations, the ...