| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| mqsideploy taking very long |
« View previous topic :: View next topic » |
| Author |
Message
|
| x061294 |
 Posted: Mon Aug 27, 2007 5:43 pm Post subject: mqsideploy taking very long |
 |
|
Acolyte
Joined: 05 Apr 2005
Posts: 62
|
We're running 6.0.0.3 of WMB on Linux, with a config mgr and Broker on one machine. We've scripted out deployments using mqsideploy and it all works. The issue is the timing. We can run an mqsideploy to remove the old flows and have it take over 20 minutes to remove them. This would be to remove maybe 15 - 25 flows.
The same process through the toolkit could be accomplished in a minute.
And the same for deployments of the flows, it can take the same amount, or longer, to deploy the same number of flows, where through the toolkit we could deploy them in just a couple of minutes.
I checked around on this before, and although there was some thought to how it maybe was because the mqsideploy command was actually running a headless version of eclipse to do the deployment, and the time was to start up eclipse, I don't know that that is true, or if there is some other reason.
Has anyone come across a similar issue, and solved it? Is there a way to speed up deployments using this command? I thought it might be a code issue due to a previous post that mentioned some issues around mqsideploy and timing, but that was supposed to be fixed in a CSD and was 3 CSD's ago, so guessing I don't have that same issue. |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Tue Aug 28, 2007 3:06 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
The difference between toolkit deploys and mqsideploy deploys, is that mqsideploy (at least in v6) waits until the broker has reported that the new message flows are actually running (or successfully removed, depending on what you were doing) before finishing. The toolkit returns as soon as the Config Manager has accepted the deploy (or flow removal request etc.).
Both methods use identical technology under the covers (i.e. the Config Manager Proxy). So it's most likely is that the deploy times are actually similar, it's just that you get control back in the Toolkit a while sooner. To find this out, when deploying from the toolkit how long is it before the Event Log viewer gets updated with the deploy success messages? The times should be similar.
If it still is a lot quicker in the toolkit, then ensure you're on the latest fixpack (as you say, there was a defect in this area previously) and raise a PMR. In the mean time, you can use the -w flag on mqsideploy to reduce the time taken to return control to you.
Regards
-Matt
PS. mqsideploy has never used Eclipse headless mode. |
|
| 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
|
|
|
|
