UIM - websphere_mq probe - Getting error in MQ monitoring - com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2495'

book

Article ID: 195830

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

After configuring MQs in wesphere_mq probe, I am getting below alarm:

QM_BRI_ACCUM_TEST is not responding (reason: Connection and/or inventory update failure) {com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason 

Cause

Websphere_mq Probe version - 2.22

Environment

Release : Any UIM release

Component : UIM - WEBSPHERE_MQ

Resolution

This problem usually occurs when you've configured your application to connect in BINDINGS mode (rather than CLIENT mode), and the Java MQ classes are unable to find the native library mqjbnd which is required to connect in BINDINGS mode.

BINDINGS uses shared memory to communicate with the queue manager rather than TCP, and requires the mqjbnd library to do this. BINDINGS mode is faster than CLIENT.

CLIENT uses TCP and doesn't require the mqjbnd native library.

To have the mqjbnd library available, your application must be running on the same physical machine as the queue manager. If you're not, you must use CLIENT.

If you're on 7.1+, then the easiest way is to run setmqenv to setup your environment prior to running your application. If you're on 7.0 then you need to do this manually by setting the Java library path - MQ_JAVA_LIB_PATH=/path/to/mqinstall/java/lib (or lib64 if you're a 64-bit JVM).""