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
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!

Meet the .conf26 AI Agent Buildathon Winners

At the .conf26 AI Agent Buildathon, Splunk users turned their operational expertise into working AI agents ...

Trusted Autonomy in the SOC: A Maturity Journey

AI is compressing attacker timelines and pushing SOC teams beyond human capacity thresholds. The next SOC ...

Supercharging Windows Security Detection Performance: Introducing Hybrid Field ...

Windows event logs—from Security auditing and Sysmon to PowerShell script blocks—form the operational backbone ...