Connection error after updating from 3.1.2 to 3.3.5

[MichalPopielski]

Dear All,
After upgrading mq-jms-spring-boot-starter from 3.1.2 to 3.3.5 I started to get error while connecting to MQ servers (different ones):

Failed to connect to queue manager '*' with connection mode 'Client' and host name ''.; nested exception is com.ibm.mq.MQException: JMSCMQ0001: IBM MQ call failed with compcode '2' ('MQCC_FAILED') reason '2298' ('MQRC_FUNCTION_NOT_SUPPORTED').

Everything works fine with the same setup/configuration on 3.1.2.
Can you please advise?

Best regards
Michał

[wirowka]

@ibmmqmet - this issue is blocking our migration to 3.3.5 (needed to verify: #117 (comment)) , we use mTLS to connect/authenticate to MQ server (no passwords) - any idea what can be wrong here?

[ibmmqmet]

No real idea. There's not a lot of diagnostic info provided to go on here. Configuration? Full stack trace? Details of the qmgr (platform/version perhaps)?

The empty hostname looks a bit odd, but I can't really tell anything else.

MQRC_FUNCTION_NOT_SUPPORTED will sometimes mean the client is trying to do something that the qmgr cannot handle - like it's very backlevel.

[wirowka]

hi @ibmmqmet
Maybe we found the root cause, not sure.
We do not want to put qmgr name since on the other site we connect to a load balancer and the data vendor from time to time does switch migration to another qmgr with the same configuraton, but differrent name
So we used configuraton like:
queueManager: "*"
In 3.1.2 it worked in 3.3.5 we are getting the MQRC_FUNCTION_NOT_SUPPORTED
MQ server version: 9.3.0.21
Since qmgr for MQ clients (as far as I remember) is not mandatory, how to configure it properly.

Edit: that was the coincidence, the root cause was ssl bundles which were introduced in the 3.3 - we did not use them so far and without them our connectors did not work properly