ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Deploying the flow using command prompt on windows.

Post new topic  Reply to topic
 Deploying the flow using command prompt on windows. « View previous topic :: View next topic » 
Author Message
sirisha.n
PostPosted: Wed Aug 27, 2008 8:02 pm    Post subject: Deploying the flow using command prompt on windows. Reply with quote

Apprentice

Joined: 25 Feb 2008
Posts: 27

Hi,

I trying to deploy the bar file using command promt. I am getting following exceptions.

1) C:\MY WORK\IDD052_NEW\Servers>mqsideploy -i localhost -p 2414 -q WBRK6_DEFAULT_QUEUE_MANAGER -b WBRK
6_DEFAULT_BROKER -e IDD052_EG -a IDD052.bar
BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1045I: Connecting to the Configuration Manager...
BIP1039I: Deploying BAR file 'C:\MY WORK\IDD052_NEW\Servers\IDD052.bar' to broker 'WBRK6_DEFAULT_BRO
KER' (execution group 'IDD052_EG') ...
BIP1100E: Broker WBRK6_DEFAULT_BROKER had not responded before the timeout occurred.

And in the event log the following error,it shows.

2) BIP2066E: Broker WBRK6_DEFAULT_BROKER (UUID 071a97cb-1701-0000-0080-c31d565ac5d3) was unable to retrieve an internal configuration response message for execution group 'IDD052_EG' within the 360 second Configuration Timeout.

The execution group did not respond within the Configuration Timeout period. A negative response is returned to the Configuration Manager for this execution group. The Configuration Timeout is the maximum length of time that an execution group is allowed to apply a deployed configuration change. By default the Configuration Timeout period is 300 seconds. You can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationTimeout. This will not resolve any underlying problem with the deployed message, but can be used to reduce the response turnaround time or increase it to allow for large and complex deployments.

Investigate why the execution group was unable to respond before being timed out. Use the system log messages to determine if there is a problem with the execution group. You should check that your system is not running short of resources, for example, you may need to increase the WebSphere log size. Reducing the complexity of the deploy by reducing the number of execution groups may also help to alleviate this problem. Correct the problem and redeploy the broker's configuration from the Message Brokers Toolkit, mqsideploy command or Config Manager Proxy. If there are no other failure diagnostics then you should consider increasing the Configuration Timeout, increase this value in units of 300 until this message no longer occurs. Contact your IBM support center if you are unable to resolve the problem.

Please suggest.

If i deploy same bar file in the broker,it is sucessfully deploying. and i can able to executee the flow.

Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Aug 27, 2008 8:51 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Increase your timeout using the mqsideploy parms.

If I understand correctly: when you use the Toolkit the deployment is successful; when you use the command line you time out...

Is your command line timout approximately the same as the toolkit time out?

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Sridar
PostPosted: Wed Aug 27, 2008 9:30 pm    Post subject: Reply with quote

Acolyte

Joined: 14 May 2006
Posts: 72
Location: Chennai, India

Hi srisha

are the values of the parameters in the command prompt correct/

In a toolkit the details are automatically taken except for the Broker name and the Bar file.

Should the bar file complete path be given?
_________________
Thanks and Regards
Sridar
Back to top
View user's profile Send private message
Ravee Bhat
PostPosted: Wed Aug 27, 2008 9:58 pm    Post subject: Reply with quote

Apprentice

Joined: 28 Apr 2004
Posts: 28
Location: Bangalore, INDIA

Had a similar issue sometime back.
A restart of QM, CM solved it for me. Did not really understand what was wrong though!!

cheers
Ravee
_________________
Lets go see The World.
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Deploying the flow using command prompt on windows.
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.