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!

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...

Splunk MCP & Agentic AI: Machine Data Without Limits

Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization uses ...