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 » Clustering » Channel Triggering and Clustering.

Post new topic  Reply to topic
 Channel Triggering and Clustering. « View previous topic :: View next topic » 
Author Message
duffMan
PostPosted: Thu Aug 15, 2002 2:47 am    Post subject: Channel Triggering and Clustering. Reply with quote

Voyager

Joined: 03 Jun 2002
Posts: 75

How does channel triggering work with clustering?

I look at the SYSTEM.CLUSTER.TRANSMISION.QUEUE and notice that it is configured (by default I am assuming) as TRIGGER ON FIRST.

Since there is only one transmission queue for a possible many sender channels, what happens in this scenerio?

* No messages on SYSTEM.CLUSTER.TRANSMIT.QUEUE
* Two Cluster Sender channels, TO.QMGRA and TO.QMGRB, both autodefined.
* QMGRA is not available.
* First message arrives on SYSTEM.CLUSTER.TRANSMIT.QUEUE, this message is bound for QMGRA but sits there because QMGRA is not available and hence the channel TO.QMGRA is in RETRY.
* SYSTEM.CLUSTER.TRANSMIT.QUEUE now has a depth of 1.
* Second message arrives on SYSTEM.CLUSTER.TRANSMIT.QUEUE, this time however it is bound for QMGRB which is available.
* Channel TO.QMGRB is inactive and must be triggered in order to deliver the second message.

What I am experiencing is that the second message just sits on the SYSTEM.CLUSTER.TRANSMIT.QUEUE as the channel TO.QMGRB never gets triggered and I will then see a queue depth of 2.

Has anyone else experienced this?

The obvious quick-fix solution is to never let channels disconnect, and ensure they are started when the queue manager is started. But this also has negative implications.

I am using MQv5.2 CSD04 for AIX 4.3.3.

Thanks,
Jason.
Back to top
View user's profile Send private message
bduncan
PostPosted: Thu Aug 15, 2002 8:10 am    Post subject: Reply with quote

Padawan

Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley

In all the clustered environments I have worked with, the channels were always-on, so we never ran into this issue. Hmm.. I would have assumed the queue manager would start the appropriate channel regardless of how many messages were on the transmission queue...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator
Back to top
View user's profile Send private message Visit poster's website AIM Address
udaybho
PostPosted: Thu Aug 15, 2002 10:53 am    Post subject: Reply with quote

Voyager

Joined: 09 May 2002
Posts: 94
Location: Chicago

Jason,

I had experience this type of behaviour in past, but in my case both sender and target queue managers were repository queue managers.

Does the QMGRA and QMGRB are Repository Queue Managers also ?

Uday Bhosle
Back to top
View user's profile Send private message Send e-mail
duffMan
PostPosted: Thu Aug 15, 2002 12:27 pm    Post subject: Reply with quote

Voyager

Joined: 03 Jun 2002
Posts: 75

QMGRA is a REPOSITORY, QMGRB is not.


Jason.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » Channel Triggering and Clustering.
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.