After upgrading Splunk DB Connect from version 3.4.0 to 3.17.1, user may encounter an error "Error in 'dbxquery' command: External search command exited unexpectedly". Below is the reference screenshot:
While validating logs, the following error was found:
2024-06-11 12:34:31.549 Trace-Id=8b618495-0395-4484-be91-5734774a82e0 [DBX-QUERY-WORKER-0] ERROR com.splunk.dbx.command.DbxQueryServer - operation= connection_name= stanza_name= action=dbxquery_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:256)
at com.splunk.dbx.command.DbxQueryServer.lambda$handleQuery$3(DbxQueryServer.java:160)
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:842)| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |