Caching of connections is not working or amount of connections increased unexpectedly

[ydrozhdzhal]

After upadting our application to Spring Boot 3.5.7 usage and switching to mq-jms-spring-boot-starter 3.5.7 our application start obtaining connection issues with server with the following root cause:

Error stacktrace

After checking server logs and other stuff we figured out that instead of creating 4 connections as it was in version 3.5.5 application created 16 connections - nothing was changed in configuration or amount of queue listeners. This was above the limit of connections and was causing issues.

Our JMS configuration

Can you look and analyze/fix such behavior? I spent a lot of time and didn't find anything that can be the root cause of this issue.

[ibmmqmet]

No reason I can think of. And of course, this library does not actually create connections itself, but just gets the configuration sorted out. Running a quick test, I don't see any difference in the number of connections made comparing 3.5.5 against 3.5.7.

I can't see anything relevant in the Spring Framework or Spring Boot release notes; nor is there anything in the MQ 9.4.4 update info. You might need to capture traces to see where the Connections/Sessions are being created. And then look at either Spring or MQ support.