When the MQ Server connection is lost ,the MQListner activity throws Null pointer exception indefinitely and reconnection doesn't take place even if the MQ Server is up later.
Article ID: KB0081845
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for IBM MQ | 8.5.0 |
Description
If we configure a process to listen on an MQ Queue, after creating an MQListerner BW Process, if we stop the MQ QueueManager from the server side we get the following log message.
*****
Error connecting to queue manager: [MQRC_Q_MGR_NOT_AVAILABLE]
*****
If we restart the MQ Server, the re-connection is not established and java.lang.NullPointerException can be seen. The application (BW Studio) goes into a hang state. This issue occurs because when a single connection stops and starts from the MQ server side, BW is waiting for a response from the MQ server for an earlier connection session and BW goes into a hung state.
Environment
Tibco ActiveMatrix BusinessWorks 6.3.5
Resolution
In order to solve this issue, use "Pooling enabled" present under "Pooloing Configuration" while creating a new shared connection resource. Pooling enabled connections solves the issue because polling is only deciding the number of active connections to the queue manager that can be set to more than one. If one connection goes into a hung state it will transfer data through another connection.
Issue/Introduction
When an MQ Server connection is lost ,the MQListner activity throws a Null pointer exception indefinitely and reconnection does not take place even if the MQ Server is up.
Feedback
Yes
No
Powered by
