| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| error in Eventviewer while deploying the message flow |
« View previous topic :: View next topic » |
| Author |
Message
|
| WBI_User21 |
 Posted: Fri Dec 07, 2007 1:50 am Post subject: error in Eventviewer while deploying the message flow |
 |
|
Voyager
Joined: 12 Jun 2007
Posts: 98
|
Hello MBIans,
"( CMGR) Broker 'BRK32' (UUID 'f2c816db-1401-0000-0080-8ba2c899ea80') execution group '''' (UUID '0b710523-1501-0000-0080-a0606fbe5597') detected that the deployed configuration message received contained an invalid XML tag.
The configuration message received could not be applied to the broker's configuration. This could occur for either of the following reasons: (a) The configuration message XML tag directs an execution group to be created but the execution group already exists. (b) The configuration message XML tag directs an execution group to be changed but the execution group does not exist. The configuration message is rejected.
Use the Message Brokers Toolkit, mqsideploy command or Config Manager Proxy to redeploy to the execution group. Contact your IBM support center if you are unable to resolve the problem. "
Can any one provide the reason for above warning.
I am working on MB6.0 on Winxp OS
Thanks in advance.. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Dec 07, 2007 2:07 am Post subject: Re: error in Eventviewer while deploying the message flow |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| WBI_User21 wrote: |
I am working on MB6.0 on Winxp OS
|
Patched to what level of Toolkit and Broker?
Does the configuration message ask for the creation of a possibly existing EG? Or the deletion of a non-existing one? What is the history of this error, i.e. what happened immediately before this error came out and did it involve creating or deleting an EG?
Have you tried one of the resolution strategies in the error message? What happened when you did (further errors etc)?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| samar14 |
| Posted: Wed Dec 12, 2007 12:23 am Post subject: |
|
|
Novice
Joined: 30 Nov 2007
Posts: 17
|
The said error usually occurs if the EG UUIDs in configmgr
repository are out of sync with what is deployed to broker.
You can use mqsibrowse command to look for the Execution
group UUIDs in broker's database (BROKERAAEG table) and
compare them with Confirmgr repository entries in CBROKER
(CXMLData column and CSECTION SHARED & DEPLED) and CEG table.
You can browse the contents of configmgr's internal
repository using 'mqsicmrv' command. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Dec 12, 2007 3:36 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Samar14- please, please don't start jumping into the broker and Config Manager's internal tables as soon as you get an error message; it's how brokers get corrupted.
Look for simple explanations first... like trying to deploy new nodes to an older broker. As Vitor says, having the fixpack details and more information will help. |
|
| 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
|
|
|
|
