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