MQSeries.net :: View topic - SNDR channel INITIALIZING after QM bounce

PeterPotkay · Posted: Mon May 24, 2004 2:37 pm Post subject:

All machines in question are Windows 2000. MQ 5.3 CSD4. Being Windows boxes, you know what that means - monthly security patches with reboots! Yay!!!!

These regular server reboots have surfaced the following issue in 2 of my 4 environments. I have a channel which needs to be up pretty much all the time, so I have the DISCINT set to 300000. And the channel speed is set to fast (probably not relevant). This channel goes from QM1 to QM2, and it has a partner going from QM2 to QM1. The channels perform as expected when the QMs are running.

When the QMs get bounced, this channel (which was running when the QM went down) comes up ready for more message in all 4 environments from QM1 to QM2, and from QM2 to QM1 in the LAB and in PROD. But in DEV and QA, the QM2.QM1.FAST channel always comes up as initializing, and stays that way until I manually start it.

All the servers and MQ versions are identical.
All the channels are defined identically (really, they are).

The only difference I can see is when I browse the SYSTEM.CHANNEL.SYNCQ. On the problem channels, the corresponding message in the SYNCQ looks like it was put by AMQPCSEA.EXE. But for all the SNDR channels that don't come up INITIALIZING (they trigger normally), the corresponding message in the SYNCQ was put by runmqchl.exe. The last 100 bytes of each message in the SYNCQ is all garbled, so I can't tell what it means or if there is a difference between the "good" channels and the "bad" channels.

Any idea why these channels keep coming up in INITIALIZING mode, and then why they are stuck in INITIALIZING mode until I issue START?

In the error log on the sending side, I see the following, until I manually restart the channel. A weird error, since the channel is most definitely there, just stuck in INITIALIZING.