| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message Broker 6 "Execution Group not running" in |
« View previous topic :: View next topic » |
| Author |
Message
|
| brokerqs |
 Posted: Wed Oct 25, 2006 5:41 pm Post subject: Message Broker 6 "Execution Group not running" in |
 |
|
Newbie
Joined: 11 Oct 2006
Posts: 4
|
Hi,
I'm running Message Broker 6 and Toolkit on Win 2003 Server. I stopped some MB components and MQSeries in Services and rebooted.
I could previously run the Pager and Web Services samples from the Samples Gallery. Now, when I try to setup the samples and deploy to run, I keep getting the alert "Execution group is not running".
This is the error in the log file in metadata:
Creating the new execution groups and deploying the samples; please wait.
Status ERROR: com.ibm.etools.mft.eou code=0 Could not create the execution groups.
Collected output from task >
Stdout: []
Stderr: [] java.lang.Exception: Could not deploy the sample's bar file.BIP1510E: Deployment failed; a deployment is already in progress to broker WBRK6_DEFAULT_BROKER
By the way, in case it was not clear, I'm interacting with broker and doing deployment from Message Broker Toolkit
Any suggestions please? |
|
| Back to top |
|
 |
| Dhiren |
| Posted: Wed Oct 25, 2006 6:32 pm Post subject: |
|
|
Novice
Joined: 27 Jan 2005
Posts: 17
|
brokerqs,
After ensuring all teh components are started ... U can try 'cancell deployment' first and then issue deploy again. It should be fine. You may be trying to deploy while there is already a deployment in progress.
| Quote: |
Stderr: [] java.lang.Exception: Could not deploy the sample's bar file.BIP1510E: Deployment failed; a deployment is already in progress to broker WBRK6_DEFAULT_BROKER
|
an excerpt from the doc...
The Configuration Manager allows only one deployment to be in progress to each broker at any one time. If for some reason a broker does not respond to a deployment request, subsequent requests cannot reach the broker, because, to the Configuration Manager, a deployment is still in progress.
Canceling deployment tells the Configuration Manager to assume that a broker will never respond to an outstanding deploy. In most cases, the action does not remove any deployment messages that have been sent to the broker, nor does it alter the running configuration of the broker.
All the best !! |
|
| Back to top |
|
|
| brokerqs |
| Posted: Wed Oct 25, 2006 7:57 pm Post subject: |
|
|
Newbie
Joined: 11 Oct 2006
Posts: 4
|
Dhiren,
I already did try to cancel the request. The same error keeps persisting.
I'm not sure if I have all componenets running though.
In Services under Admin Tools in windows, I've checked that the followiung services are running:
MQSeries
DatabaseInstanceManager6
Default broker and
Default configuration manager
During the set up for the pager sample, it gets to the point of "Creating the new execution groups and deploying the sample", then fails. |
|
| Back to top |
|
|
| narendrach |
| Posted: Thu Oct 26, 2006 12:30 am Post subject: |
|
|
Voyager
Joined: 29 Jun 2005
Posts: 78
|
Hi
try to find this .ini file
mqsicfgutil.ini
in your installation directory and edit the file with your queuemanager,port,etc
in MB5 you can find the file this directory
C:\Program Files\IBM\WebSphere Business Integration Message Brokers\bin
and try to run this command it removes all the previous deployment request's
mqsideploy -b <Broker_Name> -cancel -r -w 10
_________________
Narendra CH |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Nov 01, 2006 6:46 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
...on v6, simply right click the broker and select 'Cancel Deployment'.
Then try the deployment again. If you get the 'Deployment Initiated' message back when you do this (but when you try it a second time it fails), then the broker probably isn't picking up your deployment messages.
First make sure that you have channels set up and running between the Config Manager and broker. Look for messages piling up on the SYSTEM.BROKER.* queues and/or one of the transmission queues used to communicate between the two machines.
Also make sure that the broker and execution groups are actually running - check the system event log for errors. |
|
| 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
|
|
|
|
