MQSeries.net :: View topic

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » BIP2062E issue

BIP2062E issue

« View previous topic :: View next topic »

Author

Message

MQMD

Posted: Wed Jun 20, 2007 5:46 am Post subject: BIP2062E issue

Apprentice

Joined: 03 May 2007
Posts: 45

I am getting following BIP messages at the time of deployment.

BIP2087E
Broker WMBBRK01 was unable to process the internal configuration message.

BIP2064I

BIP2064I

BIP2062E
detected that the deployed configuration message received contained an invalid XML tag

I have deleted my broker and config manager using commands
mqsideleteconfigmgr, mqsideletebroker but still there is no improvement.

My flows are running fine.

Can any body guide why these messages are appering though commands mqsideleteconfigmgr, mqsideletebroker are used to clear any older configuration.

jefflowrey

Posted: Wed Jun 20, 2007 5:57 am Post subject:

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

How can you deploy anything if you deleted your configmgr?

How can your flows be running if you deleted your broker?

Did you follow the recommendations for resolving a BIP2062 message?
_________________
I am *not* the model of the modern major general.

MQMD

Posted: Wed Jun 20, 2007 8:34 pm Post subject:

Apprentice

Joined: 03 May 2007
Posts: 45

BIP2062 Broker <insert_0> (UUID <insert_1>) execution group <insert_2> (UUID <insert_3>) detected that the deployed configuration message received contained an invalid XML tag.

Severity: 20 : Error

Explanation: 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.

Response: 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.

(a) The configuration message XML tag directs an execution group to be created but the execution group already exists

I am deploying new execution group .So this is not the case.

(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.

I am not sending any delta message .So this is again not applicable

Since neither of the above is the case .I thought of recreating my broker and config manager
For this following commands were executed.

mqsistop cfgmgr
mqsistop brkr
mqsideleteconfigmgr cfgmgr
mqsideletebroker brkr
mqsicreatebroker brkr â€¦..
mqsicreateconfigmgr cfgmgrâ€¦.
mqsistart brkr
mqsistart cfgmgr

But still the problem exist.So I put the question

Quote:

Can any body guide why these messages are appering though commands mqsideleteconfigmgr, mqsideletebroker are used to clear any older configuration.

I hope i make more sense now jeff

fjb_saper

Posted: Wed Jun 20, 2007 8:49 pm Post subject:

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

when deleting broker and configmgr you should have made sure you dropped the involved databases. Recreating the broker/configmgr with the same databases is just going to give you the same problem if you did not delete the DB.

Enjoy

_________________
MQ & Broker admin

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » BIP2062E issue

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