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 » 2 Queue Manager, 2 Different Queues, 1 Cluster, MQPUT proble

Post new topic  Reply to topic
 2 Queue Manager, 2 Different Queues, 1 Cluster, MQPUT proble « View previous topic :: View next topic » 
Author Message
yitbos
PostPosted: Wed Mar 27, 2002 2:04 pm    Post subject: Reply with quote

Newbie

Joined: 26 Mar 2002
Posts: 3
Location: Irvine, CA

I have 2 Queue Manager (QM1 & QM2) in a cluster (MYCLUSTER). Both have full repository of MYCLUSTER. On QM1 I have a queue called Q1 and on QM2 I have a queue called Q2. I can put messages to Q2 from QM1 but I can not put messages on Q1 from QM2. Any ideas?? When I displayed the queues in the cluster, on QM1 I can see both queues (Q1 & Q2) while on QM2 I can only see Q2. I tried to refresh my cluster but I am still having the same problem.

[ This Message was edited by: yitbos on 2002-03-27 14:36 ]
Back to top
View user's profile Send private message
bduncan
PostPosted: Wed Mar 27, 2002 3:05 pm    Post subject: Reply with quote

Padawan

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

First question (check the obvious): While you made the queue managers in a cluster (MYCLUSTER) when you created each queue (Q1, Q2) did you make them members of the cluster too? i.e., DEFINE QL(Q1) CLUSTER(MYCLUSTER)
Otherwise they operate like normal local queues....


_________________
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
yitbos
PostPosted: Wed Mar 27, 2002 4:02 pm    Post subject: Reply with quote

Newbie

Joined: 26 Mar 2002
Posts: 3
Location: Irvine, CA

Yes, I did make them part of the cluster MYCLUSTER. I created Q1 on QM1 first. After doing this I can see that it is a part of MYCLUSTER by displaying the cluster queues. I then created Q2 on QM2, but after displaying the cluster queues, I can see Q1 & Q2 on QM2 and only Q1 on QM1. Can this be a bug on MQSeries V5.2 on the AS/400? It's like after creating the first queue (Q1) it took that as the master repository and won't send any changes/addition to the repository from any other Queue Manager in the cluster.

[ This Message was edited by: yitbos on 2002-03-27 16:07 ]
Back to top
View user's profile Send private message
bduncan
PostPosted: Thu Mar 28, 2002 12:55 pm    Post subject: Reply with quote

Padawan

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

Yes, I did make them part of the cluster MYCLUSTER. I created Q1 on QM1 first. After doing this I can see that it is a part of MYCLUSTER by displaying the cluster queues. I then created Q2 on QM2, but after displaying the cluster queues, I can see Q1 & Q2 on QM2 and only Q1 on QM1.
-Have you tried issuing the DIS CLUSQMGR command? This shows all the queue managers in the cluster (rather than queues in the cluster). This command will:

Use the DISPLAY CLUSQMGR command to display cluster information about queue managers in a cluster. If you issue this command from a queue manager with a full repository, the information returned pertains to every queue manager in the cluster. If you issue this command from a queue manager that does not have a full repository, the information returned pertains only to the queue managers in which you have an interest. That is, every queue manager to which you have tried to send a message and every queue manager that holds a full repository.

So this command should show both QM1 and QM2 regardless of which machine you issue it on. If you don't see both, that means the repositories aren't talking to each other properly.

Can this be a bug on MQSeries V5.2 on the AS/400?
-Probably not, quite a few people are using clustering with AS/400

It's like after creating the first queue (Q1) it took that as the master repository and won't send any changes/addition to the repository from any other Queue Manager in the cluster
-If there was any inconsistency between the queue managers regarding which objects are in the cluster, a REFRESH CLUSTER(clustername) command issued on the queue manager which appears to be out of sync (in this case QM1) should cause it to renegotiate all the cluster objects with the other full repository (QM2). If this still doesn't solve the problem, then this means that cluster information is not going from QM2 to QM1 (but appears to be working from QM1 to QM2). This probably means an issue with the CLUSSDR channel on QM2, or the CLUSRCVR channel on QM1. Check the SYSTEM.CLUSTER.TRANSMIT.QUEUE on each machine to see if the depth is greater than 0.


_________________
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
yitbos
PostPosted: Fri Mar 29, 2002 11:19 am    Post subject: Reply with quote

Newbie

Joined: 26 Mar 2002
Posts: 3
Location: Irvine, CA

Thanks for the recommendations. I was able to get my environment working again after recreating the channels. I guess some how they were corrupted by removing them out of the cluster and adding them back.
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 » 2 Queue Manager, 2 Different Queues, 1 Cluster, MQPUT proble
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.