Deployment Architecture
×

Join the Conversation

Without signing in, you're just watching from the sidelines. Sign in or Register to connect, share, and be part of the Splunk Community.
Ask a Question

Unable to initialize modular input "jms" defined inside the app "jms_ta"

BrendonFlanagan
Engager
‎08-19-2013 11:51 PM

Why am I getting this error ?

I've installed a brand new latest release of splunk and the jms mq app, followed the install instructions to the letter.

Tags (1)
Reply

arunsundaram
New Member
‎03-08-2018 11:43 AM

Install jre1.7 this should fix the issue and make sure to set java home correctly and check if the lib is also updated with the same home path

0 Karma
Reply

arunsundaram
New Member
‎02-27-2018 04:53 AM

Which version of java should we install

0 Karma
Reply

splunk_ankman
Explorer
‎09-10-2017 10:39 PM

09-11-2017 06:35:31.406 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" ... 12 more
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.406

09-11-2017 06:35:31.406 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at com.splunk.HttpService.send(HttpService.java:367)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.406

09-11-2017 06:35:31.406 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:153)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.406

09-11-2017 06:35:31.406 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.jav...
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.406

09-11-2017 06:35:31.406 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:997)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.406

09-11-2017 06:35:31.406 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1103)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.406

09-11-2017 06:35:31.406 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConne...
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.406

09-11-2017 06:35:31.406 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.406

09-11-2017 06:35:31.406 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:275)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.405

09-11-2017 06:35:31.405 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.405

09-11-2017 06:35:31.405 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.405

09-11-2017 06:35:31.405 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.405

09-11-2017 06:35:31.405 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.405

09-11-2017 06:35:31.405 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:649)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.405

09-11-2017 06:35:31.405 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at java.net.Socket.connect(Socket.java:589)
Hi Am getting following errors:
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.405

09-11-2017 06:35:31.405 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.405

09-11-2017 06:35:31.405 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.405

09-11-2017 06:35:31.405 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.405

09-11-2017 06:35:31.405 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
host = gbrpsr000003527 source = /apps/pcbsplunk/splunk/var/log/splunk/splunkd.log sourcetype = splunkd
11/09/2017
06:35:31.405

09-11-2017 06:35:31.405 +0100 ERROR ExecProcessor - message from "python /apps/pcbsplunk/splunk/etc/apps/jms_ta/bin/jms.py" at java.net.PlainSocketImpl.socketConnect(Native Method)

PLease help me out

0 Karma
Reply

arunsundaram
New Member
‎03-14-2018 10:12 AM

have you fixed the issue

0 Karma
Reply

stonemason
Engager
‎09-13-2013 06:38 AM

I don't know if you have exactly the same problem. I just saw this message on a splunk system after installing the JMS Messaging Modular Input App:
"Unable to initialize modular input "jms" defined inside the app "jms_ta": Introspecting scheme=jms: script running failed (exited with code 1)"

The problem here was that $JAVA_HOME was not available in splunk and also java was not set in the standard PATH. So Splunk could not call JAVA.
The app uses JAVA in /opt/splunk/etc/apps/jms_ta/bin/jms.py

0 Karma
Reply

Damien_Dallimor
Ultra Champion
‎08-20-2013 03:14 AM

Have you followed the troubleshooting steps in the docs ?

0 Karma
Reply

BrendonFlanagan
Engager
‎08-20-2013 12:26 AM

Yes I did, and the logs were no help what so ever, just re-itterated the same error, no reason, no other errors.

0 Karma
Reply

sbsbb
Builder
‎08-19-2013 11:56 PM

Have you already looked in splunkd.log for more information about what's going wrong ?

0 Karma
Reply
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!

Index This | What travels the world but is also stuck in place?

April 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data

Realizing the full potential of your Splunk investment requires more than just understanding current usage; it ...

Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...

As data volumes continue to grow and environments become more distributed, managing and optimizing data ...