Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Getting error : WebSphere MQ reason code 2538?

I have WebSphere MQ and WebSphere Message Broker installed on Linux and when I execute mqsicreateexecutiongroup I get an error saying:

BIP1046E: Unable to connect with the queue manager (Could not connect to queue manager 'NSPZPAI1' (MQ reason code 2538)).

When I search for this reason code I understand that it is a host not available error.
Can somebody please tell me how to resolve this error?

When I run a runmqlsr command I always end up in a hang. Can somebody tell me how to start a listener?

like image 353
Tanu Avatar asked Oct 16 '12 09:10

Tanu


People also ask

What is a MQ error?

IBM MQ error logs are the combination of system error logs, queue manager error logs, and first failure data captures.

How do I know if MQ listener is running?

The START LISTENER command starts the listener. You also have STOP LISTENER MQSC command to stop the listener. Once you create and start the listener, you can then issue DISPLAY LSSTATUS command to display the listener status.

Could not establish a connection to the queue manager as a connection is already in progress?

This could be because the queue manager is incorrectly configured to allow a connection from this system, or the connection has been broken. Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded. win aix both have user(mq) .

What is IBM WebSphere MQ used for?

The main use of IBM WebSphere MQ is to send or exchange messages. One application puts a message on a queue on one computer, and another application gets the same message from another queue on a different computer.


2 Answers

Don't start the listener by hand or script. If you have a modern queue manager, define a listener object like so:

DEF LISTENER(LISTENER.1414)  TRPTYPE(TCP) +
    CONTROL(QMGR)            PORT(1414) +
    REPLACE

START LISTENER(LISTENER.1414)

The attribute CONTROL(QMGR) tells the QMgr to start the listener automatically when the QMgr is started and to kill the listener when the QMgr is shut down. This ensures that the listener will always be started when the QMgr comes up, even if the QMgr is started manually instead of from the usual boot script. Because the listener is a child process of the QMgr it will always come down with the QMgr so you don't need to worry about orphaned listeners preventing connections after a QMgr restart.

Once the listener is defined, you can also use START LISTENER or STOP LISTENER MQSC commands to manually start and stop it independently of the QMgr. In the example above, I've manually started the listener rather than reboot the QMgr. Either would work but the START command is less intrusive.

like image 191
T.Rob Avatar answered Oct 25 '22 23:10

T.Rob


Listener is run using

runmqlsr -t tcp -p <port> -m <queue manager name>.

It starts the listener which waits for connections. More details on the command are here

like image 43
Shashi Avatar answered Oct 26 '22 00:10

Shashi