All Apps and Add-ons

JMS Messaging Modular Input 1.7.2 - Connection poller error: Connection refused

jor_jorsy
Loves-to-Learn

We are trying to get the JMS inputs to work (connecting to MQ Series) but when the jms.py script is launched to initialise the modular input, we get the following java exception:
Error executing modular input : Connection refused (Connection refused) : java.lang.RuntimeException: Connection refused (Connection refused)
at com.splunk.HttpService.send(HttpService.java:370)
at com.splunk.Service.send(Service.java:1268)
at com.splunk.HttpService.get(HttpService.java:151)
at com.splunk.Entity.refresh(Entity.java:381)
at com.splunk.Entity.refresh(Entity.java:1)
at com.splunk.Resource.validate(Resource.java:174)
at com.splunk.Entity.validate(Entity.java:462)
at com.splunk.Entity.getContent(Entity.java:157)
at com.splunk.Entity.getString(Entity.java:279)
at com.splunk.ServiceInfo.getVersion(ServiceInfo.java:155)
at com.splunk.modinput.ModularInput.runStateCheckerThread(Unknown Source)
at com.splunk.modinput.ModularInput.init(Unknown Source)
at com.splunk.modinput.jms.JMSModularInput.main(Unknown Source)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:666)
at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173)
at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:264)
at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConne...
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.jav...
at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:167)
at com.splunk.HttpService.send(HttpService.java:367)
... 12 more
The java command that produces the exception is:
['/usr/lib/jvm/jre-1.8.0/bin/java', '-classpath', '/opt/splunk/etc/apps/jms_ta/bin/lib/*', '-Xms64m', '-Xmx64m', '-Dsplunk.securetransport.protocol=tls', '-Dsplunk.logging.level=INFO', 'com.splunk.modinput.jms.JMSModularInput', '\n\n XXXXXXXX\n https://10.10.10.10:8089\n epqigvRtJ3ZebVjWyp4d^C965IlejTAKbdt3i5CCbcTnapuYMWFO8zyK9kzINFwbYnfC\n /opt/splunk/var/lib/splunk/modinputs/jms\n \n \n ...

The java command with the "--scheme" option works fine:
['/usr/lib/jvm/jre-1.8.0/bin/java', '-classpath', '/opt/splunk/etc/apps/jms_ta/bin/lib/*', '-Xms64m', '-Xmx64m', '-Dsplunk.securetransport.protocol=tls', '-Dsplunk.logging.level=INFO', 'com.splunk.modinput.jms.JMSModularInput', '--scheme']
08/20/2019 17:19:14 - root - INFO - Java process output is INFO Initialising Modular Input
INFO Getting scheme
INFO Data sent to Splunk:
JMS Messaging
Poll messages from queues and topics
true
xml
true



JMS queue or topic
...

Any idea what could be wrong here?

0 Karma

baboonbones
New Member

You'll find the best support for this App at the author's Slack community channel.Sign up here if you don't already have access : https://www.baboonbones.com/#support

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...