IBM MQ message channel is not coming up

Question

I am trying to setup message channel on IBM MQ v8.

I am running IBM MQ Server 8.x on Ubuntu Linux.

I have 2 queue managers QM1, and QM2.

On QM1, I have created a Sender Channel, and on QM2, I have created a Receiver channel.

On QM1:

Remote queue definition

DEFINE QREMOTE(RMQ1) DESCR('Remote queue for QM2') REPLACE +
PUT(ENABLED) XMITQ(QM2)  RNAME(Q_ON_QM2) RQMNAME(QM2)

Transmission queue definition

DEFINE QLOCAL(QM2) DESCR('Transmission queue to QM2') REPLACE +
USAGE(XMITQ) PUT(ENABLED) GET(ENABLED) TRIGGER TRIGTYPE(FIRST) +
TRIGDATA(QM1.TO.QM2) INITQ(SYSTEM.CHANNEL.INITQ)

Sender channel definition for a TCP/IP connection:

DEFINE CHANNEL(QM1.TO.QM2) CHLTYPE(SDR) TRPTYPE(TCP) +
REPLACE DESCR('Sender channel to QM2') XMITQ(QM2) +
CONNAME('127.0.0.1(**1491**)') //-- QM2's listener is on 1490

On 2nd Queue manager (QM2)

Local queue definition

DEFINE QLOCAL(Q_ON_QM2) REPLACE PUT(ENABLED) GET(ENABLED) +
DESCR('Local queue ')

Receiver channel definition

For a TCP/IP connection:

DEFINE CHANNEL(QM1.TO.QM2) CHLTYPE(RCVR) TRPTYPE(TCP) +
REPLACE DESCR('Receiver channel from QM1')

At the end of configuration, my sender channel remains in "Retrying" state, and Receiver channel remains in "inactive" state.

How do I get this channel running?

Answer 1

At first glance, it appears the problem is with your port. The conname for connection should specify the port where the listener is actually running. Is it 1491 or 1490?

CONNAME('127.0.0.1(1491)') //-- QM2's listener is on 1490

Verify the listener is running for the receiving qmgr and specify that port in your conname.

Answer 2

There could be many reasons of a sender channel going in retrying state.

1. Wrong parameters.

Check connection name as Valerie suggested. Make sure IP address and port number points to the receiver queue manager.

2. Transmission queue unavailable.

Make sure the transmission queue is available. Note: Sometimes the transmission queue will be available but it might be GET disabled, in that case also the sender channel will go in retrying state. The sender channel opens the transmission queue in exclusive mode, which means if the transmission queue is opened by another application (say RFHUTIL), then the sender channel will not be able to access transmission queue and hence the channel will go in retrying state. So, make sure the transmission queue is not opened by some other application.

3. Receiver channel unavailable.

This could be the case when the receiver queue manager is down. Also, make sure the name of receiver channel is same as the sender channel(which seems correct in your case).

4. Receiver channel and sender channel go out of sequence

The receiver channel and sender channel maintains a sequence number for message transmission. Due to environmental issues like network glitches, the sequence number might become inconsistent between the sender and receiver channel.

RESET your sender and receiver channels to overcome this issue.