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
Get Updates on the Splunk Community!

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...

Introducing the 2024 Splunk MVPs!

We are excited to announce the 2024 cohort of the Splunk MVP program. Splunk MVPs are passionate members of ...