| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP1510E Unable to deploy to the broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| Janesd |
 Posted: Thu Mar 06, 2008 6:34 am Post subject: BIP1510E Unable to deploy to the broker |
 |
|
Newbie
Joined: 28 Feb 2008
Posts: 5
|
Hi All
I am getting the following error while deploying a flow to MQ server
BIP1510E: Unable to deploy configuration data.
I've tried stopping the Queue manager and starting again but it didn't work
| Code: |
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 SBB_BROKER1. 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 Event Log Editor 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 by specifying the 'Cancel' option in the Message Brokers Toolkit Note that 'Cancel' affects all outstanding deployment operations throughout the domain, so you may not have the authority to perform this.
|
Any suggestions on how to solve it ? |
|
| Back to top |
|
 |
| SAFraser |
| Posted: Thu Mar 06, 2008 7:49 am Post subject: Re: BIP1510E Unable to deploy to the broker |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
| Janesd wrote: |
| Code: |
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 SBB_BROKER1. 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 Event Log Editor 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 by specifying the 'Cancel' option in the Message Brokers Toolkit Note that 'Cancel' affects all outstanding deployment operations throughout the domain, so you may not have the authority to perform this.
|
Any suggestions on how to solve it ? |
The message tells you exactly what to do.
If it still does not complete, then cancel the deploy operation by specifying the 'Cancel' option in the Message Brokers Toolkit Note that 'Cancel' affects all outstanding deployment operations throughout the domain, so you may not have the authority to perform this.
Cancel the deployment, using either the Toolkit or the Config Mgr Proxy API Exerciser (if you want to cancel only the one broker's deployment).
You mention that your queue manager is running. Both of them? Are the channels running or are the xmitqs set to trigger? After you cancel your deployment, start both sets of channels to be sure that the Config Mgr can talk to your target queue manager. |
|
| Back to top |
|
|
| Janesd |
| Posted: Fri Mar 07, 2008 6:00 am Post subject: |
|
|
Newbie
Joined: 28 Feb 2008
Posts: 5
|
Hello
thank you very much for your reply..i know this might seem odd to you, but i'm completely new to this...how can i cancel the deploy operation using the exerciser or the toolket as advised? i went through the toolket and the API but couldn't figure out how to cancel the deployment..
many thanks.. |
|
| Back to top |
|
|
| Janesd |
| Posted: Fri Mar 07, 2008 6:25 am Post subject: |
|
|
Newbie
Joined: 28 Feb 2008
Posts: 5
|
Hii guys
I right-clicked on the connected MQ server and chosed "Cancel Deployment" and it worked!!!
thanks for your helpful tips and hints  |
|
| Back to top |
|
|
| SAFraser |
| Posted: Fri Mar 07, 2008 7:06 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
Janesd,
I am glad you figured out how to cancel a deployment. But you did not right click "the connected MQ server". You right clicked the WMB broker. The difference between an MQ server and a WMB broker is vast. They are not the same product, nor do they serve similar purposes.
I am a little concerned that you are deploying things to brokers at this stage of your "new-ness". Please spend some time looking through Links and Repository on this site! And good luck with your new responsibilities.
Shirley |
|
| 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
|
|
|
|
