All Apps and Add-ons

Splunk MINT: How do we prevent our app from crashing when the Splunk Java SDK throws an exception?

neerajjindal201
New Member

We had a recent scenario where Splunk was throwing a null pointer exception and it caused our app to crash. This happened only on September 9 (after months of testing on our side and no changes to our Splunk calls). We had many many crashes and subsequent bad reviews. The crashes stopped occurring after something (again) changed on the Splunk server.

Here is a stack trace:

java.lang.NullPointerException
at com.splunk.mint.RemoteSettings.convertJsonToRemoteSettings(SourceFile:38)
at com.splunk.mint.ActionEvent.send(SourceFile:93)
at com.splunk.mint.Mint$2.run(SourceFile:183)
at java.lang.Thread.run(Thread.java:856)

Other than making sure using the latest version of the SDK, we want to add something in our code that catches all exceptions from the SDK so we don't get bad reviews in and when the Splunk server has a problem.

How do we do this?
Meaning, is there something we can override, put a try catch around or...whatever you recommend so we don't get crashes from you?

0 Karma

croyal_splunk
Splunk Employee
Splunk Employee

The September 2015 issue lasted approximately 3 hours. We're sorry for the negative impact. The team did add additional safeguards and we do not expect similar issues in the future.

You can track Known Issues for iOS and Android SDKs.

0 Karma
Get Updates on the Splunk Community!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

🔐 Trust at Every Hop: How mTLS in Splunk Enterprise 10.0 Makes Security Simpler

From Idea to Implementation: Why Splunk Built mTLS into Splunk Enterprise 10.0  mTLS wasn’t just a checkbox ...

Observe and Secure All Apps with Splunk

  Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...