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!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...