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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...