Installation

Java Bridge Server not working after JDK upgrade

sroback_splunk
Splunk Employee
Splunk Employee

Hi.

We updated JDK on our Red Hat servers from version 1.6 to 1.7. Now our DB Connect App shows the Java Bridge Server is not running. And the dbx.log contains the following error messages:

2014-05-02 10:30:05.286 dbx6162:ERROR:TailDatabaseMonitor - Error while executing database monitor: com.splunk.dbx.DbxException: Error getting database connection: Pool not open
com.splunk.dbx.DbxException: Error getting database connection: Pool not open
at com.splunk.dbx.sql.factory.PooledConnectionFactory.getConnection(PooledConnectionFactory.java:72)
at com.splunk.dbx.sql.Database.getConnection(Database.java:508)
at com.splunk.dbx.sql.Database.prepare(Database.java:206)
at com.splunk.dbx.monitor.impl.TailDatabaseMonitor.performMonitoring(TailDatabaseMonitor.java:94)
at com.splunk.dbx.monitor.DatabaseMonitorExecutor.executeMonitor(DatabaseMonitorExecutor.java:126)
at com.splunk.dbx.monitor.DatabaseMonitorExecutor.call(DatabaseMonitorExecutor.java:102)
at com.splunk.dbx.monitor.DatabaseMonitorExecutor.call(DatabaseMonitorExecutor.java:37)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.IllegalStateException: Pool not open
at org.apache.commons.pool.BaseKeyedObjectPool.assertOpen(BaseKeyedObjectPool.java:156)
at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1109)
at com.splunk.dbx.sql.factory.PooledConnectionFactory.getConnection(PooledConnectionFactory.java:70)
... 14 more

Anyone know what might be causing this? Recommendations for a fix? Thanks!

1 Solution

ilink_splunk
Splunk Employee
Splunk Employee

This error occurs when the JDK version referenced in the path to JAVA_HOME inside the DB Connect app does not match the JDK version installed on the server. dbx.log will show an "Error_getting_database_connection:_Pool_not_open" message. The resolution for this issue can be found in the troubleshooting section of the DB Connect app docs.

View solution in original post

ilink_splunk
Splunk Employee
Splunk Employee

This error occurs when the JDK version referenced in the path to JAVA_HOME inside the DB Connect app does not match the JDK version installed on the server. dbx.log will show an "Error_getting_database_connection:_Pool_not_open" message. The resolution for this issue can be found in the troubleshooting section of the DB Connect app docs.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Meet Splunk Observability Studio: AI-Assisted OpenTelemetry Instrumentation Without ...

Instrumentation is usually the last step or even an afterthought when building out a project. The feature ...

Federated Search for Cisco Security and Analytics Logging (SAL) is now GA on Splunk ...

Federated Search for Cisco  Security Analytics and Logging (SAL) is now generally available as part of the ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Join us for a demo-driven look at how ...