Now I know how important is MQ Client .

We had configured HA Queue manager, WAS and 3rd party JMS application.

On Node 1 :- QM was active
JMS application was active
WAS was active
On Node 2 :- QM was passive
JMS application was active
WAS was active

Issue was :-

JMS Application on Node 1 was able to connect MQ but JMS Application on Node 2 wasn't.
It was throwing 2059 error . When we switched QM active on Node 2 then the JMS application node 2 was able to connect the queue manager but Application on node 1 wasnt and was throwing the same error 2059. We tried to configure many a times but didnt find any success. We struggled almost 2 days to figure out the problem

Solution :-

We used /opt/mqm/bin/samp/bin/amsputc on node where QM was passive. It gave us error libmqic.so file not found. Then we figured out the MQ Client software is missing so any JMS Application cannot connect remote queue manager.

After Installing MQClient rpm and setting binding mode as MQ Client , the problem resolved.. Finally we got it right. Thanks amqsputc for throwing that error.

Cheers
-Manju

Websphere MQ

I see MQ as set of meaningfull files managed by applications. Being so simple concept it is rock solid product by IBM.