[SOLVED] Handle out of sync point issue via IBM JMS from Mule

Handle out of sync point issue via IBM JMS from Mule

I am connecting MQ-8.x from Mule via JMS and recently I had faced an issue that seems like MQ write operation is going out of sync point range and due to this and also the huge inbound load, MQ went in to deadlock state.

<spring:bean id="ConnectionFactory" class="com.ibm.mq.jms.MQConnectionFactory" name="ConnectionFactory">
        <spring:property name="hostName" value="xxxx" />
        <spring:property name="port" value="xxxx"/>
        <spring:property name="queueManager" value="xxxx"/>
        <spring:property name="transportType" value="1"/>
        <spring:property name="channel" value="xxxx"/>
   </spring:bean>

<jms:connector name="JmsConsumer" username="xxxx" password="xxxx" specification="1.1" connectionFactory-ref="ConnectionFactory"  numberOfConsumers="1" validateConnections="true"  persistentDelivery="true" doc:name="JMS"/> 

<jms:outbound-endpoint queue="xxxx" connector-ref="JmsConsumer" doc:name="Audits"/>

My operation volume will be move but its just a PUT operation, so I am really not sure whether XA or other Transaction manager to be needed in this.

Solution

This has been handled in MQ-9.x version that MQ itself will manage the out of sync point implicitly. MQ-9.x upgrade will be the solution for this kind of issue.

https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.dev.doc/q026865_.html