| Author |
Message
|
| brokerics |
 Posted: Fri Nov 25, 2005 5:26 am Post subject: mqsilist |
 |
|
Apprentice
Joined: 30 Oct 2005
Posts: 45
|
hi
when i issue a mqsilist command,
its shows
BIP8099I: BKQM - BKQM
BIP8099I: BQM - BQM
BIP8099I: BROK - MYBRKQM
BIP8099I: BROOK - BROOK
BIP8099I: ConfigMgr - MYCFGQM
BIP8099I: TBROK - BROK
BIP8099I: WBIBRK - BRKQM
BIP8071I: Successful command completion.
but they're all old brokers except BQM,my current broker( config mgr same)
and im not able to deploy to BQM
the event logs say the config mgr is still deploying to BROOK or BROK.
someone there to help? |
|
| Back to top |
|
 |
| brokerics |
| Posted: Fri Nov 25, 2005 5:27 am Post subject: |
|
|
Apprentice
Joined: 30 Oct 2005
Posts: 45
|
| oh..and those old brokers...were deleted by me |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Nov 25, 2005 5:28 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you delete these old brokers?
successfully?
Both from the tooling and with mqsideletebroker?
In the right order?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| brokerics |
| Posted: Fri Nov 25, 2005 6:10 am Post subject: |
|
|
Apprentice
Joined: 30 Oct 2005
Posts: 45
|
i deleted them from both
but if ure askin if i did it chronologically... i doubt it
how do i figure it out? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Nov 25, 2005 6:25 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I meant, did you delete each broker first from the tooling and then using mqsideletebroker. That is, delete them properly, rather than improperly.
Did the toolkit deploys complete successfully?
Does the toolkit topology show the old brokers, or not?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| brokerics |
| Posted: Fri Nov 25, 2005 6:31 am Post subject: |
|
|
Apprentice
Joined: 30 Oct 2005
Posts: 45
|
yes i deleted ..from tool first ..then using mqsi
but the toolkit deploys successfully only..how?
the toolkit does not SHOW the old brokers...but the event log message sometimes says the configuration message was successul in case of the old broker, inspite of it not bein there |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri Nov 25, 2005 7:09 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| brokerics wrote: |
| but the toolkit deploys successfully only..how? |
I assume you're using V5 - in which case, right click the Broker topology in the toolkit and select 'Deploy Topology Configuration -> Complete'.
What does the Config Manager's event log (i.e. double click on Event Log in toolkit) show after doing this? You should get messages saying that the Configuration Manager has tidied up references to the broker.
Once you've got these messages, then you can go ahead and mqsideletebroker.
But, given that you're still seeing the brokers in mqsilist, it looks as though the mqsideletebroker step hasn't been completed successfully. Did you get errors when you ran this? What did the command output say? Also, did you get errors in the OS event log? |
|
| Back to top |
|
|
| brokerics |
| Posted: Sun Nov 27, 2005 9:09 pm Post subject: |
|
|
Apprentice
Joined: 30 Oct 2005
Posts: 45
|
yes..i use v5 broker.
i din exactly get any message like it has tidied up references to the broker but whenever i deploy to a new broker(BQM), it shows
BIP2062E: Broker BQM (UUID 9a9f7fbc-0701-0000-0080-c9dbb625d028) Execution Group 'TF' (UUID aeb269c7-0701-0000-0080-c9dbb625d028) 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.
Use the Message Brokers Toolkit to redeploy to the Execution Group. Contact your IBM support center if you are unable to resolve the problem.
now i got this for a simple msg flow, just mqinput and mqoutput..no xml domains.
i never got any error while deletin using mqsideletebroker command. the command was successful.
the OS log says
( ConfigMgr ) Unprocessable response received by Configuration Manager on input queue SYSTEM.BROKER.ADMIN.REPLY.
A message was received by the Configuration Manager on input queue SYSTEM.BROKER.ADMIN.REPLY, but the message was not a response to an outstanding broker request. Either this message has erroneously appeared on queue SYSTEM.BROKER.ADMIN.REPLY, or a Message Brokers Toolkit user has deployed configuration data to a broker with the 'forced' option which removes details of any outstanding deploy request. The message has been written to the WebSphere Business Integration dead letter queue.
Look at the message on the dead letter queue to establish which application sent the message. If the message was a reply from a broker to which a deploy was subsequently cancelled, then it can be safely ignored. Otherwise correct the application.
any clues? |
|
| Back to top |
|
|
| brokerics |
| Posted: Sun Nov 27, 2005 9:13 pm Post subject: |
|
|
Apprentice
Joined: 30 Oct 2005
Posts: 45
|
| since i guess it has not tidied up references, and i deleted them, how do i clear them out? |
|
| Back to top |
|
|
| brokerics |
| Posted: Sun Nov 27, 2005 9:31 pm Post subject: |
|
|
Apprentice
Joined: 30 Oct 2005
Posts: 45
|
alsoooo in the event log, theres one more
BIP2064I: Broker BQM (UUID 9a9f7fbc-0701-0000-0080-c9dbb625d028) Execution Group '' (UUID d1c5b7c1-0701-0000-0080-c9dbb625d028), deployed configuration message rejected.
This Execution Group's configuration message was rejected because the deployed configuration message would have caused more serious errors in other Execution Groups. This Execution Group was not the primary cause for the rejection of this configuration message.
Look at all the messages that were listed and resolve the problems that they describe. The Execution Group mentioned in this message can be deployed individually. |
|
| Back to top |
|
|
|
|
