We were losing the defs on the partial repository qms. The solution for us was to define a static clussdr from a full repos to each partial repos. We had defined the cluster relying on dynamic clussdr channels from the full repos qms to the partial repos qms. That is, we had defined static clussdrs from partial to full, but allowed MQ to auto define the clussdr from full to partial based.
Scott -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Tony Boggis Sent: Monday, September 20, 2004 9:40 PM To: [EMAIL PROTECTED] Subject: Re: Disappearing cluster queues I'm not sure I follow... Are you saying that on each FULL-REPOS, have an additional CLUSSDR channel? So that would mean that each full repository holder having one CLUSSDR channel to another full repos and a second CLUSSDR to a partial repos (cluster member) queue manager? tonyB. > -------- Original Message -------- > Subject: Re: Disappearing cluster queues > From: "Scott Gray" <[EMAIL PROTECTED]> > Date: Mon, September 20, 2004 6:28 pm > To: [EMAIL PROTECTED] > > We had that problem between sun/hp and z/os...we were told to have at > least one static cluster sender between full repository and leaf node. > We were relying on dynamic clussdrs from full repos to leaf node. > Once we did this, that problem has not reoccured. No explanation for > the behavior was provided by IBM. > > Good luck. > > Scott > > -----Original Message----- > From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Tony > Boggis > Sent: Monday, September 20, 2004 9:18 PM > To: [EMAIL PROTECTED] > Subject: Disappearing cluster queues > > > Puzzling situation... > > Environment: Solaris, WMQ 5.3 CSD05. > > I have a cluster with about 24 queue managers each on it's own host. > All are "sharing" one or more queues in the cluster, eaching being > unique, giving 200+ queues. > > Periodically cluster queues "disappear" on some hosts, leaving me > getting 2085 errors, even from amqsput. Manually refreshing the > cluster (REFRESH CLUSTER) usually does the trick. Usually. > > All my CLUSSDR/CLUSRCVR channels are configured and none are > Binding/Retrying, etc. I have 4 full-respository managers defined, all > are up and running. > > This is not 60+ days or anything that would obviously point to cluster > expiration. > > tonyB. > > Instructions for managing your mailing list subscription are provided > in the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > Instructions for managing your mailing list subscription are provided > in the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
