| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| execution group problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| rkford11 |
 Posted: Fri Sep 03, 2004 1:28 pm Post subject: execution group problem |
 |
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
BIP2062E: Broker KBRKR (UUID 2f8b9ab0-fe00-0000-0080-8f65fbd99b47) Execution Group 'default' (UUID 3f8b9ab0-fe00-0000-0080-8f65fbd99b47) 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 any of the following reasons: The configuration message XML tag directs an execution group to be created but the execution group already exists. The configuration message XML tag directs an execution group to be changed but the execution group does not exist. The configuration message is rejected.
thanks |
|
| Back to top |
|
 |
| kirani |
| Posted: Fri Sep 03, 2004 10:24 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Please provide more details. When exactly do you get this error? What version of WMQI/WBIMB are you using?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| rkford11 |
| Posted: Sat Sep 04, 2004 4:48 pm Post subject: execution group problem |
|
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
| kirani wrote: |
| Please provide more details. When exactly do you get this error? What version of WMQI/WBIMB are you using? |
i am using version 5.0 and i got this error when i tried to deploy the bar file created on my system on to the execution group running on the server. config mgr and broker are on the server with using respective queue managers |
|
| Back to top |
|
|
| JT |
| Posted: Sat Sep 04, 2004 8:59 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
|
| Back to top |
|
|
| dadalee |
| Posted: Mon May 30, 2005 9:32 pm Post subject: duplicate Execution group under 'Operation' tab error. |
|
|
Newbie
Joined: 30 May 2005
Posts: 1
|
I encountered a same issue however I am using 2.0,
my initial cause of problem was duplicated EG in the same broker, causing two instances of msgflows competing for messages from the same Input queue. While I try to fix this problem by removing the execution group from the 'Assignments' tab I noticed only one EG exists while under the 'Operations' tab there were two EG with the same name. After trying lots of remove/delete/redeploy, MQSI got angry with me while I try to stop the the EG which doesn't exists:
BIP2062E: Broker AxisBroker (UUID e7bbfc9b-f900-0000-0080-8b5f49c51881) Execution Group '' (UUID d19fb8d4-0301-0000-0080-b0367faa26ca) detected that the deployed configuration message received contained an invalid XML tag.
The configuration message received could not be applied to the brokers configuration. This could occur for any of the following reasons: The configuration message XML tag directs an execution group to be created but the execution group already exists. 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 Control Center to redeploy the complete configuration for the Execution Group. Contact your IBM support center if you are unable to resolve the problem.
Notice that the the EG is '' (an EG with empty name).
and from now on every delta/complete deploy will cause:
BIP1510E: Unable to deploy configuration data.
An attempt was made to deploy configuration data to one or more brokers, but the Configuration Manager is already deploying to broker AxisBroker. You can not deploy to a set of brokers if there is an earlier deploy outstanding to any broker in the set. The deploy operation was not performed.
Wait for the outstanding deploy to complete before retrying the operation. The Log view may be used to check that all responses to the outstanding deploy have been received and processed. If the outstanding deploy does not fully complete in a suitable period of time, check that all brokers exist and are running, all MQSeries queue managers are running, and that all channels between queue managers are started. Also check that deploy messages have been correctly delivered to the target brokers, and have not been put to the dead letter queue. Correct any problems you find. If it still does not complete, then retry the deploy operation specifying the 'Forced' option which overrides any outstanding deploy. Note that 'Forced' causes all configuration throughout the entire domain to be redeployed so you may not have authority to perform this. The 'Forced' option may only be selected when deploying 'Complete configuration (all types)' from the File menu.
I think was a deployment request made to CM for the removed EG. However I need a solution that will retract/cancel the any pending deployment. Note that I am using MQSI 2.1 and even I use IC01 - mqsideploy I cannot find the [-cancel] switch as in V5. My another approach is to do a 'Force' deployment, which eventually crashed when JVM is out. (I have this set to the maximum and even though my Broker is too big for it)
I need a solution to resolve this issue, can anyone give me some pointers on how I can fool MQSI to ignore all previous deployment request.
or
A method to do FORCE deployment on one EG per time.
or
A possible quick database fix if it was corrupted. eg, by manually remove any bad entries.
or any feasible methods for a huge Broker. Thanks in advance. |
|
| 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
|
|
|
|
