All Apps and Add-ons

JMS Modular Input and MQ - SSL Error

rahul927
Explorer

The Queue Manager is on the same machine as the JMS TA. We have specified transport as Bindings mode in the JMS Topic Connection Factory. It works fine, messages are subscribed. However the mq logs show
The SSL or TLS connection was closed by the remote host during the secure socket handshake. The channel is '????' in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Process (2252:8402) User (mom) Program(amqrmppa) Host Installation (Installation 1) VRMF QMGR
The TCP/IP responder program encountered an error.

Does the JMS mod input try the client connection by default and then look for bindings mode?
If so can we avoid it from connecting using client connection.

0 Karma

Damien_Dallimor
Ultra Champion

Does the JMS mod input try the client
connection by default and then look
for bindings mode? If so can we avoid
it from connecting using client
connection.

This is in no way controlled by the JMS Mod Input code. This is determined by how you setup your Bindings file in MQ , which I believe also has settings for controlling the SSL behaviour

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

 Are you ready to revolutionize your IT operations? As digital transformation accelerates, the demand for ...

Calling All Security Pros: Ready to Race Through Boston?

Hey Splunkers, .conf25 is heading to Boston and we’re kicking things off with something bold, competitive, and ...

Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...

Financial services organizations face an impossible equation: maintain 99.9% uptime for mission-critical ...