| Author |
Message
|
| letsmq |
 Posted: Wed Jul 07, 2004 12:33 am Post subject: problem with deploy |
 |
|
Newbie
Joined: 02 Jul 2004
Posts: 2
|
Installed message broker on XP. with bothe COnfigration manager and broker installed on same box (though under different Queue managers).
I had a previous deploy working fine.
Tried modifying a msgflow and then re-deploying.
The sequence followed was -
1. stopping the deploy
2. removing the deploy
3. modifying the esql and msgflow
4. Adding the new msgflow to bar file
and
5. Deploy again.
On doing so, I get the following error message -
BIP1510E: Unable to deploy configration data.
An Attempt was made to deploy configration data to one or more brokers, but the configration manager is already deploying to broker WBRK_BROKER. you cannot deplot to a set of brokers if there is an earlier deploy outstanding to any broker in the set. The deploy was not performed.
Wait for the outstanding deploy to complete ........."
I have never understood why it thinks an old deploy is present there. Additionally, I tried creating new Execution group - but that comes with same error msg.
Is there a way out of this.....
Please advice.... |
|
| Back to top |
|
 |
| wooda |
| Posted: Wed Jul 07, 2004 12:49 am Post subject: |
|
|
Master
Joined: 21 Nov 2003
Posts: 265
Location: UK
|
BIP1510E: occurs when the configmgr is waiting on a response from a deploy to a broker.
It wont start a new deploy until it knows the outcome of a previous deploy.
There are a number of reason why a deploy response may not have been received.
- Check your channles are still running.
- Check your broker is still running.
- Wait a little while for the response to come (a few minutes will be more than enough)
If everything seems to be in order and you still get no response you can force a redeploy.
Right click on the domain icon in the Domains view in the Broker Admin perspective. Select "Cancel Deployment". This will allow you to do another deploy.
Hope this helps
- Alex |
|
| Back to top |
|
|
| wooda |
| Posted: Wed Jul 07, 2004 12:52 am Post subject: |
|
|
Master
Joined: 21 Nov 2003
Posts: 265
Location: UK
|
BTW -
You should always check you got a response from a deploy to see if it worked.
The pop-up window only tells you that the deploy was sent not if it worked.
Use the Event Log view in the Broker Admin perspective to see responses to deploys. Check for a successful response. |
|
| Back to top |
|
|
| wooda |
| Posted: Wed Jul 07, 2004 12:57 am Post subject: |
|
|
Master
Joined: 21 Nov 2003
Posts: 265
Location: UK
|
BTW -
You should always check you got a response from a deploy to see if it worked.
The pop-up window only tells you that the deploy was sent not if it worked.
Use the Event Log view in the Broker Admin perspective to see responses to deploys. Check for a successful response. |
|
| Back to top |
|
|
| Jack W. Khaw |
| Posted: Thu Jul 08, 2004 10:48 am Post subject: you have 2 Queue Managers. Correct? |
|
|
Newbie
Joined: 08 Jul 2004
Posts: 7
|
If this is true, then you will need sender and receiver channels for them to communicate. This is what I have on my XP prtending that the Broker is on AIX/Solaris.
_________________
jkhaw |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Jul 08, 2004 11:31 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
And make sure the maxmessage length on channels, xmit queue is set to large number. You might get some error when trying to deploy large message sets/flows.
Also make sure the XMIT queue name is same as your target queue manager name.
_________________
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 |
|
|
|
|
