Hi everyone, I am working on an application that routinely monitors splunk logs via the splunk Java api, and collects metrics. Essentially, multiple threads are created, each that makes a call to the Service using oneshotsearch method. The program works fine for a while, but eventually they all get bombarded with the Http 401 response. I did some research, it I've seen posts that say the current session could be expired and the user needs to re-login to Splunk. TO try and combat this, I have the service "re-login" using my splunk credentials, whenever it gets this response back. However, it doesn't look like this has fixed the issue... Does anyone have any experience with this exception/ could provide me with some info to help troubleshoot? ... View more

Hi All, I am using the Java splunk api service to make oneShotSearch calls for service data. HTTP 503 response: Search not executed: The maximum number of concurrent historical searches on this instance has been reached.", concurrency_category="historical", concurrency_context="instance-wide", current_concurrency=34, concurrency_limit=34 What I am doing is creating multiple threads which perform the Service#oneshotSearch in given time intervals. It runs normally, but eventually, I get the HTTP 503 above error. I am not that familiar with Splunk (mainly focusing on the Java code) so could someone please elaborate on what this exactly means? I am confused what exactly instance is referring to, is this referring to a specific host included in the queries, or is this referring to my own user searches once I am logged in? I do not have 34 threads, so are they getting backed up and queued through the api? If anyone could please provide me with some details on this error to help troubleshoot, I would greatly appreciate it. Thank You! ... View more