Hi Folks,
Using Spring-boot application with asynch receive JMS listener (various recent versions of spring). Working against a windows multi-instance QM (9.2). See two things:
1) Either the connection never re-appears after fail-over. This happens occasionally and usually around two fail-overs after an exception has been registered at the JMS listener.
2) The connection appears, however the asynch state of the connection is inactive (as if spring is using a stale connection perhaps?) . I can get this to occur with just a few fail-overs on a regular basis.
I've tried using multiple Spring containers from the SimpleJms container through to the default container.
I can't repeat the issue when I use ibm-mq-spring-boot library. However, this lib is not supported (hmmm).
My worry is this
1) I use the ibm-mq-spring-boot lib and it is masking the issue and the issue will reappear later
2) There is an underlying issue with the base MQ JMS auto-reconnect that spring boot just happens to be bringing to the surface quicker than if we weren't using it.
Can anyone confirm that they have thoroughly tested the MQ JMS Auto-reconnect behaviour within a spring environment?
Presumably asynch re-connection is supported by IBM with spring? How come the ibm-mq-spring-boot lib works - the code doesn't look that complex but clearly doing enough to not get this issue?
thanks for any help on this !
John.
------------------------------
John Hawkins
Integration Consultant
------------------------------