Author |
Message
|
anantha sreenivasan |
Posted: Sun Sep 30, 2007 9:09 pm Post subject: Deployment Problem |
|
|
Acolyte
Joined: 26 Sep 2006 Posts: 72
|
I have a broker named Broker1 with Execution Group BROK_EG1. I depolyed two message flows to it. Now when try to deploy a message flow to another broker say Broker2 in the same broker domain as Broker1, I get the following warning
BIP1510E: Deployment failed; a deployment is already in progress to broker BROKER2
The Configuration Manager was asked to deploy to broker BROKER2, but this could not be attempted because it has not yet received a response to a previous deployment request submitted to that broker. To ensure that the deployed configuration is consistent with the reported configuration, the more recent deployment request has been discarded.
Note that if you are attempting to deploy the publish/subscribe topology or topic hierarchy, no brokers in the domain will have received the new deployment message. There can be no outstanding deploys in the domain before deployment of such a configuration can occur.
Wait for the outstanding deploy to complete before retrying the operation. The Event Log Editor or Configuration Manager Proxy 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 WebSphere MQ 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 cancel the deploy operation; either (a) right-click the broker in the Message Brokers Toolkit and select the 'Cancel Deployment' option, (b) use mqsideploy with the -c option, or (c) or use the BrokerProxy.cancelDeployment() method in a Configuration Manager Proxy application. Note that cancelling the deployment operation does not stop the deployment message from being processed by the broker; it simply forces the Configuration Manager to remove any outstanding deployment locks that may be associated with the broker. If a broker subsequently processes a deployment message that has been cancelled using this technique, the deployed configuration may become inconsistent with the reported configuration.
I cancelled all outstanding deployment against this broker and started afresh. Even after that I get the same problem. Can somebody please advise? |
|
Back to top |
|
 |
elvis_gn |
Posted: Sun Sep 30, 2007 9:34 pm Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi anantha sreenivasan,
Please don't double post....it won't get you speedy replies...
Regards. |
|
Back to top |
|
 |
AkankshA |
Posted: Sun Sep 30, 2007 10:55 pm Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
did you get a successfull deployment responce when you added broker into configMgr domain...
try a delta topology deployment and see if it works.... _________________ Cheers |
|
Back to top |
|
 |
anantha sreenivasan |
Posted: Sun Sep 30, 2007 11:07 pm Post subject: |
|
|
Acolyte
Joined: 26 Sep 2006 Posts: 72
|
The above described error is failure deployement response |
|
Back to top |
|
 |
AkankshA |
Posted: Sun Sep 30, 2007 11:12 pm Post subject: Re: Deployment Problem |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
anantha sreenivasan wrote: |
BIP1510E: Deployment failed; a deployment is already in progress to broker BROKER2
|
says that deployment is already happening....
so in that case as suggested in the error a cancel deployment shall help... and try deploying the delta topology (this shall ensure that broker n configMgr repositories are in sync)
also do check the system logs for any probable cause of other error... _________________ Cheers |
|
Back to top |
|
 |
Gaya3 |
Posted: Sun Sep 30, 2007 11:38 pm Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
Check if any messages are lying in the queue
System.Broker.admin.queue
if any messages are lying and its not getting processed, you have to investigate.
Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
anantha sreenivasan |
Posted: Mon Oct 01, 2007 3:10 am Post subject: |
|
|
Acolyte
Joined: 26 Sep 2006 Posts: 72
|
As you said there is 1 message stalled in SYSTEM.BROKER.ADMIN.QUEUE
How to investigate this? |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Oct 01, 2007 3:12 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
You will probably need to bounce the broker....  _________________ MQ & Broker admin |
|
Back to top |
|
 |
AkankshA |
Posted: Mon Oct 01, 2007 3:14 am Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
delete the msg and bounce the broker
after that try delta topology deployment first and on successfull completion of that u can try deploying your flows _________________ Cheers |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Oct 01, 2007 3:24 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
AkankshA wrote: |
delete the msg and bounce the broker
after that try delta topology deployment first and on successfull completion of that u can try deploying your flows |
Deleting the message should always be looked at as an extreme measure with extreme consequences... in other words avoid unless directed to do so by IBM...
This might mean that you need to do a full topology deployment, redeploy all your flows in all your execution groups...
Anyways, before deleting such a message I would try and inspect the content to see the extent of the damages....
Now if the message on the queue says 'test message', has nothing to do with the broker and was put there by some misguided attempt to use a test tool to put a message I will not hesitate and delete it...
Most of the time just recycling the broker and a little bit of patience will do the trick.
 _________________ MQ & Broker admin |
|
Back to top |
|
 |
|