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
.conf21 CFS Extended through 5/20!

Don't miss your chance
to share your Splunk
wisdom in-person or
virtually at .conf21!

Call for Speakers has
been extended through
Thursday, 5/20!