Posted: Wed Nov 26, 2003 5:15 am Post subject: Channel stops by itself after MQ v5.3 upgrade
Apprentice
Joined: 09 Oct 2002 Posts: 36
Hello!
Running qmgr HUB on AIX machine AIXPROD. We are hub and spoke. Spoke qmgr SPK1 lives on Win2k machine, also running MQ v5.3 CSD05. Another spoke qmgr is SPK2 residing on AIX machine AIXPROD running MQ v5.3 CSD05.
.
Problem Description:
Prior to upgrading from MQ v5.2 CSD04 to MQ v5.3 CSD05 we found that a sender channel could only ever go into 'STOPPED' status when someone with authority issued the 'stop' command. We saw no exceptions, ever. Now, after upgrading to MQ v5.3 CSD05 we see our sender channel HUB.TO.SPK1 go 'stopped' overnight and after a recycle of the HUB queue manager. We haven't been able to isolate down to exactly when it occurs yet. Has something changed where a sender channel can go 'stopped' for some condition(s)? Can you please explain circumstances where a sender channel can go into 'stopped' state without someone issuing the 'stop' command? Something appears to have changed with MQ v5.3......please comment.
Thanks, Dan
JasonE - some FDC's with a SIGTERM to the runmqtrm are seen during normal shutdown at 4am. These are new also with MQ v5.3.
Under what conditions can a channel go into a 'stopped' state....? I wonder if the code base has changed with MQ v5.3 on AIX....seems the only channels that go into 'stopped' state are on AIX.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum