Reporting

Splunk Java SDK : Why does job.isDone(..) hang forever, but the job inspector in Splunk Web shows the job is done?

splunkears
Path Finder

Hello,

I'm using Splunk Java SDK. Something like the following:

...
...
while (!myJob.isDone()) {
try {
            Thread.sleep(500);
} catch (InterruptedException e) {
               e.printStackTrace();
}
}

My search query takes a long time and hangs forever at myJob.isDone()
But, when I inspect the job by going to Splunk Web's job inspector, I see the job is already done.
Can you help if something wrong with what I'm doing? or is this a known issue with Splunk 6?

Tags (4)

dwtung
Explorer

I had the same issue. Adding job.refresh() in the while !job.isDone() loop fixed it.

See this post: https://answers.splunk.com/answers/221239/splunk-java-api-why-a-job-object-savedsearchdispat.html

0 Karma
Get Updates on the Splunk Community!

Register to Attend BSides SPL 2022 - It's all Happening October 18!

Join like-minded individuals for technical sessions on everything Splunk!  This is a community-led and run ...

What's New in Splunk Cloud Platform 9.0.2208?!

Howdy!  We are happy to share the newest updates in Splunk Cloud Platform 9.0.2208! Analysts can benefit ...

Admin Console: A Single, Unified Interface for All Your Cloud Admin Needs

WATCH NOWJoin us to learn how the admin console can save you time and give you more control over the Splunk® ...