Join the Conversation
- Find Answers
- :
- Apps & Add-ons
- :
- All Apps and Add-ons
- :
- All Apps and Add-ons
- :
- Re: Java Management Extensions Add-on: Installatio...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After installing this add-on on Splunk Cloud (clustered indexing and search head tiers), the data input on the indexing tier was throwing errors like the following:
Search peer idx-i-010c268432edd8af5.REDACTED.splunkcloud.com has the following message: Unable to initialize modular input "jmx" defined inside the app "Splunk_TA_jmx": Introspecting scheme=jmx: script running failed (exited with code 1). 6/20/2019, 8:27:17 PM
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Splunk Support reported that after install the "input was trying to run on introspection".
Upshot: After installing add-on, Splunk Support may need to disable the input.
NOTE: It took quite a while to get through this. I reported the errors, and they couldn't seem to find the offending data inputs at first. (?) This is why I'm sharing here ... to help whoever else experiences this get through it faster.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Splunk Support reported that after install the "input was trying to run on introspection".
Upshot: After installing add-on, Splunk Support may need to disable the input.
NOTE: It took quite a while to get through this. I reported the errors, and they couldn't seem to find the offending data inputs at first. (?) This is why I'm sharing here ... to help whoever else experiences this get through it faster.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So what exactly was the fix for this? I have the same error using Splunk Add-on for Java Management Extensions?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Splunk support told me they couldn’t suppress the errors, so I submitted an enhancement request.
Sorry. I wish I had a better answer.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did the addon actually work? I am not getting data since Nov 4th. And no changes were made.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks like your intent is to share this information with the community. I propose you mention the problem in your question and then put the solution in answer and accept it. Or else for the users searching on this will only see this one as unanswered and might not even look.
Thanks !
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas
What Is the Name of the USB Key Inserted by Bob Smith? (BOTS Hint, Not the Answer)
Automating Threat Operations and Threat Hunting with Recorded Future
