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 » WebSphere Message Broker (ACE) Support » Odd behavior during Config Manager Migration

Post new topic  Reply to topic
 Odd behavior during Config Manager Migration « View previous topic :: View next topic » 
Author Message
nukenrg
PostPosted: Thu Oct 16, 2003 12:17 pm    Post subject: Odd behavior during Config Manager Migration Reply with quote

Newbie

Joined: 29 Apr 2003
Posts: 5
Location: Chicago, IL

Here's a good one.

We recently moved our developement and production Config Managers to some new faster Windows 2000 machines.

Since this is about the third time I've moved the environemnt in 2 years things went pretty smoothly. (Amazing how much smoother things go when you do things in the right order! )

I also used this as an opportunity to upgrade to CSD05, which I did after recreating my brokers on my Solaris servers. (10 brokers on 4 servers)

The odd thing I noticed was that, apparently when I issued the mqsicreatebroker command, the dead-letter queue reverted back to the default SYSTEM.DEAD.LETTER on each of the brokers' queue manager. At this customer's site, we always use qmgrname.DEAD.LETTER as a standard naming convention. I verified against some old reports from mqhealth from the previous week, and they were in fact named per the convention.

Sure enough, I did a dis qmgr against each and they were each altered at about the same time as I remember recreating the brokers.

This was easy enough to fix and didn't really cause any real problems. I was just curious if anyone else has seen this behavior and/or has any idea why it does this.
Back to top
View user's profile Send private message
jfluitsm
PostPosted: Mon Oct 20, 2003 11:37 am    Post subject: Reply with quote

Disciple

Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands

Thanks for this post.

We recreated a couple of brokers last week for the upgrade to version 2.1 on Solaris. We checked the QM's this morning after I read your post yesterday and indeed the DLQ was set to SYSTEM.DEAD.LETTER.QUEUE.

I think this is ok when the DLQ is not set, this will prevent messageflows from looping, however in my opinion this is a bug when the DLQ is set.
_________________
Jan Fluitsma

IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6
Back to top
View user's profile Send private message Send e-mail
nukenrg
PostPosted: Mon Oct 20, 2003 11:50 am    Post subject: Reply with quote

Newbie

Joined: 29 Apr 2003
Posts: 5
Location: Chicago, IL

Great! Glad to see it's not just me.

Leads me to wonder what else it changed that wasn't so obvious!
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 » WebSphere Message Broker (ACE) Support » Odd behavior during Config Manager Migration
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.