Update: we were able to get this resolved (I'm joshuaswink's coworker). For anyone running into this issue in the future, this appears to be an edge case code bug. We're running Splunk 10.0.1 + Splunk DB Connect 4.2.2 + Splunk DBX Add-on for Snowflake JDBC 1.2.4. We've been able to identify a workaround. Conditions: You've created a Snowflake Connection. The credentials are a part of the JDBC URL. There are no firewalls blocking the connection to Snowflake. From Snowflake's side, it looks like the transactions were successful. Symptoms: When you go to the Query Explorer and select the Connection, the Catalog, Schema, and Table will all populate correctly. Your first query after configuring the Connection may work. However, you will encounter the following error message if you try to make any more queries: "Error in 'dbxquery' command: No value present" See the splunk_app_db_connect_commands.*.log on the underlying system (e.g. at /opt/splunk/var/log/splunk/, or wherever it is for your system). You will find the following stack trace: 2026-03-24 12:48:56.916 Trace-Id=f8c20411-f4c4-4c77-aaea-2a921b387e5c [Query-Worker-50] ERROR com.splunk.dbx.command.DbxQueryServer - feature=query component=server action=handle_query status=failed message=dbx query server worker failed java.lang.IllegalStateException: I/O operation on closed writer at com.splunk.search.command.AbstractWriteHandler.checkValidity(AbstractWriteHandler.java:100) at com.splunk.search.command.AbstractWriteHandler.flush(AbstractWriteHandler.java:228) at com.splunk.search.command.ChunkedWriteHandler.flush(ChunkedWriteHandler.java:69) at com.splunk.search.command.AbstractWriteHandler.close(AbstractWriteHandler.java:233) at com.splunk.search.command.ChunkedCommandDriver.execute(ChunkedCommandDriver.java:120) at com.splunk.search.command.AbstractSearchCommand.run(AbstractSearchCommand.java:50) at com.splunk.search.command.GeneratingCommand.run(GeneratingCommand.java:15) at com.splunk.dbx.command.DbxQueryCommand.runCommand(DbxQueryCommand.java:253) at com.splunk.dbx.command.DbxQueryServer.lambda$handleQuery$3(DbxQueryServer.java:149) at com.splunk.dbx.logging.MdcTaskDecorator.run(MdcTaskDecorator.java:23) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:840) Workaround: Create an Identity and attach it to the Connection. This appears to avoid a check somewhere in the code that triggers this bug.
... View more
