ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General Discussion » messages stuck in the system.cluster.xmit.queue

Post new topic  Reply to topic
 messages stuck in the system.cluster.xmit.queue « View previous topic :: View next topic » 
Author Message
py38
PostPosted: Fri Oct 03, 2003 8:23 am    Post subject: messages stuck in the system.cluster.xmit.queue Reply with quote

Newbie

Joined: 02 Sep 2003
Posts: 8
Location: Chicago, Il USA

On the 2 repository queue managers, 8 messages destined to the a clustered remote queue manager were queued up in the system.cluster.xmit.queue. That remote manager was up and running.

The sdr chl to the destined queue manager did not show up in "dis chs(*)".

Once I manually startup that sdr chl, messages cleared up and went to that remote queue manager.

Why didn't the message in the system.cluster.xmit.queue trigger the running of the sdr channel?

We are running WMQ 5.3.0.4 on AIX.

Thanks much.
Back to top
View user's profile Send private message Yahoo Messenger
mqonnet
PostPosted: Fri Oct 03, 2003 8:35 am    Post subject: Reply with quote

Grand Master

Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.

If messages arrive when a channel is in an inactive state, the channel would be triggered. But if it was manually stopped, it needs to be started manually as well. I think if it is in a retry state, unless the cause for its retry is fixed, even if new msgs arrive, channel wont trigger and go into running state, since the problem that caused it go to retry still exists.

So, my first approach would be to see if there was anything logged in the error log around or before the time when you restarted the channel. Find the cause of it going into retry state.

Cheers
Kumar
Back to top
View user's profile Send private message Send e-mail Visit poster's website
py38
PostPosted: Fri Oct 03, 2003 11:21 am    Post subject: Reply with quote

Newbie

Joined: 02 Sep 2003
Posts: 8
Location: Chicago, Il USA

The sdr chl was in inactive state.
Error logs revealed no errors on both qmgrs.
Once the sdr was started manually. Zoom went the messages.

Why didn't the message in the sys.clus.xmit.q trigger the sdr chl?

That's what is confounding. Thanks.
Back to top
View user's profile Send private message Yahoo Messenger
mqonnet
PostPosted: Fri Oct 03, 2003 12:16 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.

Well. I cannot really tell you why it behaved this way. But are you sure your Channel initiator was running.

Cheers
Kumar
Back to top
View user's profile Send private message Send e-mail Visit poster's website
TonyD
PostPosted: Fri Oct 03, 2003 4:55 pm    Post subject: Reply with quote

Knight

Joined: 15 May 2001
Posts: 540
Location: New Zealand

This topic has been discussed in the clustering forum...suggest you look there.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General Discussion » messages stuck in the system.cluster.xmit.queue
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.