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 » message flow node id mismatch on Control center and broker

Post new topic  Reply to topic
 message flow node id mismatch on Control center and broker « View previous topic :: View next topic » 
Author Message
smaram1
PostPosted: Fri Sep 05, 2003 12:14 pm    Post subject: message flow node id mismatch on Control center and broker Reply with quote

Novice

Joined: 06 May 2003
Posts: 19
Hi,

I am trying to deploy existing flows on solaris with minor changes in flows from windows config manager.

I am getting the following error.

IP2266W: Request to change attribute in message flow node '25150c3f-ef00-0000-0080-fc05124be481': message flow does not exist.

The message broker received a configuration message containing an instruction to change an attribute in the message flow node '25150c3f-ef00-0000-0080-fc05124be481' but this message flow does not exist.

I have checked flows on Solaris Broker and the message flow id doesnt match.

I am not sure why the id's arent matching.These are the same flows that i deployed earlier. How i can get rid of flows on Solaris Broker so that i can deploy flows again? Or are there any other ways of overcoming this issue?

Any help is appreciated.

Thanks
Suresh
Back to top
View user's profile Send private message
smaram1
PostPosted: Fri Sep 05, 2003 1:00 pm    Post subject: Reply with quote

Novice

Joined: 06 May 2003
Posts: 19
More Error Info on this:

BIP4041E: Execution group 'MODS.SO.IN' received an invalid configuration message. See the following messages for details of the error.

The message broker received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of either message flows or message sets which the configuration manager was unable to detect. It can also result from a message flow requiring a type of node that is not supported by the broker installation, from the broker having become out of step with the configuration database or from other applications sending extraneous messages to the broker's configuration queues (SYSTEM.BROKER.ADMIN.QUEUE & SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).

Check the relevant message flow and message set definitions, check that all necessary plug-ins are installed, perform a complete redeploy of the broker's configuration and ensure that no applications are writing to the broker's configuration queues.
Back to top
View user's profile Send private message
smaram1
PostPosted: Fri Sep 05, 2003 4:21 pm    Post subject: solved Reply with quote

Novice

Joined: 06 May 2003
Posts: 19
I had to delete old flow node id's from DB2 database and that did the trick..

thanks for ur time..
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 » message flow node id mismatch on Control center and broker
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.