| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Cluster Repository to become "corrupted" |
« View previous topic :: View next topic » |
| Author |
Message
|
| geferra |
 Posted: Mon Jun 25, 2001 5:12 pm Post subject: |
 |
|
Newbie
Joined: 24 Jun 2001
Posts: 4
Location: IBM
|
The other issue that we are trying to get addressed and understand is what causes
the cluster repository to become 'corrupted'. When this occurs, there are no error
messages, log entries, FDC's...nothing to indicate there is a problem with the
repositories. We have not seen any issues with the SYSTEM.CLUSTER.COMMAND.QUEUE
or with messages going to the dead letter queue. |
|
| Back to top |
|
 |
| bduncan |
| Posted: Mon Jun 25, 2001 5:51 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Are you running MQSeries 5.2? We were running 5.1 in a clustered environment, and had to rebuild the cluster from scratch several times because of corrupted repositories. We were selected as a beta-tester for MQ 5.2, and were told that the likelihood of corrupt repositories was diminished because of changes between 5.1 and 5.2. From personal experience I have to agree, though we still had problems with 5.2 - but not nearly as often. That would be my first step. If you are already using 5.2, then maybe you can explain the problem more specifically. For instance, sometimes we would delete a queue manager from a cluster, and the queue manager definition for the deleted queue manager would still appear in the repositories. That is one example. This would be solved sometimes by issuing a RESET CLUSTER command to forcibly remove the definition of the deleted queue manager. Another problem we ran into is when we deleted individual queues from the clusters, sometimes the definitions would still appear on the repositories. Though this seemed to be a bad thing IBM assured us that this was just a ghost definition that would go away after 90 days, and that there was no chance the workload balancing scheme would try to send messages to the ghost queue... Hope this helps...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
