|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Urgent: deployment problem |
« View previous topic :: View next topic » |
Author |
Message
|
new2wmb |
Posted: Fri Aug 08, 2008 3:20 am Post subject: Urgent: deployment problem |
|
|
Newbie
Joined: 08 Aug 2008 Posts: 5
|
Hi ,
I am using wmb6.1 version and i have created default configuration, it was working fine till today morning, but some how it stops working now. it is showing some error while i'm deploying the flow in execution group( execution group is default execution group) while deploying bar file i'm getting following error.
Error message
BIP1510E: Deployment failed; a deployment is already in progress to broker 'WBRK61_DEFAULT_BROKER'.
A request was issued for the Configuration Manager to deploy to broker 'WBRK61_DEFAULT_BROKER'. This request cannot be processed because the Configuration Manager has not yet received a response to a previous deployment request submitted to that broker. To ensure that the deployed configuration is consistent with the reported configuration, the more recent deployment request has been discarded.
If you are deploying the publish/subscribe topology or topic hierarchy, no brokers in the domain will have received the new deployment message. There can be no outstanding deployments in the domain before deployment of such a configuration can occur.
Wait for the outstanding deployment to complete before retrying the operation. Check the Event Log editor or Configuration Manager Proxy to verify that all responses to the outstanding deployment have been received and processed.
If the outstanding deployment request does not complete in a suitable period of time, check that all brokers exist and are running, all WebSphere MQ queue managers are running, and all channels between queue managers are started. Check that deployment messages have been correctly delivered to the target brokers, and have not been put to the dead letter queue. Correct all problems that you find.
If, following these actions, the deployment does not complete, cancel the deploy operation by using one of the following methods:
1. Right-click the broker in the workbench and then selecting the 'Cancel Deployment' option, or 2. Run the mqsideploy command with the -c option, or
3. Include the BrokerProxy.cancelDeployment() method in a Configuration Manager Proxy application.
If you cancel the deployment operation, the cancelation does not stop the deployment message from being processed by the broker. It forces the Configuration Manager to remove any outstanding deployment locks that might be associated with the broker. If a broker subsequently processes a deployment message that you have canceled in this way, the deployed configuration might become inconsistent with the reported configuration.
What i did is:
1. I have checked the services , wbrk61_default_configuration_manager and wbrk61_default_broker are running just fine.
2. I did the 1st method of error message suggestions so many times i.e
Right-click the broker in the workbench and then selecting the 'Cancel Deployment' option
3. I have deleted the default configuration and created again couple of times. but still it is showing the same error.
Anybody please help me.
thanks in advance
Last edited by new2wmb on Fri Aug 08, 2008 5:11 am; edited 1 time in total |
|
Back to top |
|
 |
AkankshA |
Posted: Fri Aug 08, 2008 3:28 am Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
Please search in this forum...
Its been discussed many many times... _________________ Cheers |
|
Back to top |
|
 |
vaibhav_vy |
Posted: Fri Aug 08, 2008 3:35 am Post subject: |
|
|
Apprentice
Joined: 04 Aug 2008 Posts: 28
|
There might be database connectivity problem. You can check System events using Event Viewer to know more details. Consider removing broker only as last option. For that, try to remove default configuration & create new configuration using mqsi commands instead of Default Configuration Wizard. Using commands, you can have more flexibility. |
|
Back to top |
|
 |
new2wmb |
Posted: Fri Aug 08, 2008 3:40 am Post subject: |
|
|
Newbie
Joined: 08 Aug 2008 Posts: 5
|
I checked the eventviewer it is showing following error.
I dont think this would be resolved by increasing the time period. becase i have deployed the many bar files. i didn't get any issues with time period.
error message is
( WBRK61_DEFAULT_BROKER ) Execution group 'default' failed to return an internal configuration 'Start' message response within a 60 second time period.
The internal configuration message response could not be retrieved. The execution group therefore failed to move to the state described by the internal configuration message.
Review messages issued to the system log to investigate why the execution group internal configuration message response was not returned within the allowed time period. Additionally, you can increase (or decrease) the timeout using the mqsichangebroker parameter, InternalConfigurationTimeout. Changing the timeout does not resolve any underlying problem with a deployed configuration message, but can be used to reduce the response turnaround time, or to allow for large and complex deployments. Resolve any problems described in the system log. This internal configuration operation is retried automatically; if you continue to see this message, you should investigate the reason for the execution group's failure to respond. |
|
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
|
|
|
|