Troubleshooting the Splunk SDK for Java

This topic describes how to troubleshoot problems when coding with the Splunk SDK for Java. It contains the following sections:

If you still have questions after reading this topic, see the Questions? sidebar on the right side of this page for additional help.

An app created with the Splunk SDK for Java runs fine locally, but experiences problems running off of a Java Application Server (such as WebLogic)

Double-check the version of Java running on the server. The Splunk SDK for Java does not work on versions of Java earlier than 1.6. If your server is still using Java 1.4 or 1.5, you will need to update it to a version that provides at least Java 1.6.

Performance lag when creating a collection object (for instance, a JobCollection, UserCollection, or EntityCollection)

Such lags occur most often when the collection you are creating has many elements. The Splunk SDK for Java used to cache all elements of a collection when the collection is created, which caused this lag. This behavior should now be fixed. If you find a collection that still exhibits this behavior, please submit a bug to us at the Splunk SDK for Java GitHub repository or by e-mailing

My app won't connect over SSL anymore

You've probably updated to Java 8. The Splunk SDK for Java is compatible with Java 8. Be aware that Java 8 disables Secure Sockets Layer version 3 (SSLv3) by default, so you will need to use Transport Layer Security (TLS) instead. To see an example of how to do this, see the ssl_protocols example in the SDK. Alternatively, you can re-enable SSLv3 in Java settings, but this is not recommended.