Splunk Dev

HTTP Exception: 401 -- call not properly authenticated after a while using Java api with threads

Aweave15
New Member

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?

Tags (1)
0 Karma
Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...