| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Bar file deployment |
« View previous topic :: View next topic » |
| Author |
Message
|
| gokulam |
 Posted: Wed Apr 30, 2008 5:54 pm Post subject: Bar file deployment |
 |
|
Newbie
Joined: 17 Apr 2008
Posts: 9
|
We are running WMB 6.0.0.3. When we try to deploy a bar file which is about 4 MB we are always getting time out error inspite of we increased the timeout period to 900 seconds. We are using the toolkit to deploy the bar file.
I have the following questions.
1. Before we start deploying can we stop the broker? Will it help in response time in deployment?
2. If broker cannot be stopped when the new changes will get into effect?
3. Is there any suggestions to improve the deployment?
Thanks |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu May 01, 2008 12:01 am Post subject: Re: Bar file deployment |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gokulam wrote: |
| 1. Before we start deploying can we stop the broker? Will it help in response time in deployment? |
Yes. No.
| gokulam wrote: |
| 2. If broker cannot be stopped when the new changes will get into effect? |
As soon as the "old" version of the flow(s) in the bar file have finished procesing the last message. Changes to flows are not made mid-flight. Flows not in use at deployment time will change immediately (obviously).
| gokulam wrote: |
| 3. Is there any suggestions to improve the deployment? |
Yes - work out what's wrong! A 4Mb file isn't that large, though is suspiciously close to the default channel & queue limit! Can the infrastructure which links config mgr & broker handle that size? Does the change become effective eventually? What happens if you deploy via command line? What errors (if any) are there in the respective logs? What other resolutions have you attempted to fix this, aside from increasing the timeout limit?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu May 01, 2008 1:19 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If the broker is stopped, deployment doesn't happen.
ConfigMgr will take the deployment request, not get an answer from Broker, and return a failure message to you (eventually).
And then when broker starts, the deploy may complete.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri May 02, 2008 5:06 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| jefflowrey wrote: |
| ConfigMgr will take the deployment request, not get an answer from Broker, and return a failure message to you (eventually). |
Technically, and pedantically (so apologies in advance), you'll get an 'initiated' message back. Then, assuming that the broker accepts the deployment when it does eventually start up, the deployment will finish successfully and all of the CM, broker and user will be happy.
We normally reserve 'failure' for when things have gone 'permanently' wrong. Deploying to a stopped broker is fine, even though you won't see a 'broker has successfully processed the deployment' type message (assuming you're using mqsideploy, anyway).
-Matt |
|
| 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
|
|
|
|
