MQSeries.net :: View topic

asudhakar · Posted: Fri May 29, 2009 2:22 pm Post subject:

Hi,

While deploying bar file into EXGrp im getting following error.

Can any one kindly help how to resolve this issue.

BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1045I: Connecting to the Configuration Manager...
BIP1039I: Deploying BAR
BIP1510E: Deployment failed; a deployment is already in progress to broker BKDEV
02

The Configuration Manager was asked to deploy to broker BKDEV02, but this could
not be attempted because it has not yet received a response to a previous deploy
ment request submitted to that broker. To ensure that the deployed configuration
is consistent with the reported configuration, the more recent deployment reque
st has been discarded.
Note that if you are attempting to deploy the publish/subscribe topology or topi
c hierarchy, no brokers in the domain will have received the new deployment mess
age. There can be no outstanding deploys in the domain before deployment of such
a configuration can occur.

Wait for the outstanding deploy to complete before retrying the operation. The
Event Log Editor or Configuration Manager Proxy may be used to check that all re
sponses to the outstanding deploy have been received and processed. If the outst
anding deploy does not fully complete in a suitable period of time, check that a
ll brokers exist and are running, all WebSphere MQ queue managers are running, a
nd that all channels between queue managers are started. Also check that deploy
messages have been correctly delivered to the target brokers, and have not been
put to the dead letter queue. Correct any problems you find. If it still does n
ot complete, then cancel the deploy operation; either (a) right-click the broker
in the Message Brokers Toolkit and select the 'Cancel Deployment' option, or (b
) use mqsideploy with the -c option, or (c) use the BrokerProxy.cancelDeployment
() method in a Configuration Manager Proxy application. Note that cancelling the
deployment operation does not stop the deployment message from being processed
by the broker; it simply forces the Configuration Manager to remove any outstand
ing deployment locks that may be associated with the broker. If a broker subsequ
ently processes a deployment message that has been cancelled using this techniqu
e, the deployed configuration may become inconsistent with the reported configur
ation.

Error :

May 29 13:08:45 gen0sudev09 inetd[167]: [ID 317013 daemon.notice] MUBRKD01[29823] from 128.127.99.225 45935
May 29 13:12:41 gen0sudev09 WebSphere Broker v6005[25487]: [ID 702911 user.error] (BKDEV02.EGOTH03)[41]BIP4041E: Execution group 'EGOTH03' received an invalid configuration message. See the following messages for details of the error. : BKDEV02.115cdf37-1c01-0000-0080-c4d9c9ba7c83: /build/S600_P/src/DataFlowEngine/ImbConfigurationNode.cpp: 394: ImbConfigurationNode::evaluate: ComIbmConfigurationNode: ConfigurationNode
May 29 13:12:41 gen0sudev09 WebSphere Broker v6005[25487]: [ID 702911 user.error] (BKDEV02.EGOTH03)[41]BIP2242E: Message flow 'MF_NXGCOR_ASSET_ACC_CMPY_BAL_PYMT' could not be reconfigured because it remained busy for longer than the timeout period of '300000' : BKDEV02.115cdf37-1c01-0000-0080-c4d9c9ba7c83: /build/S600_P/src/DataFlowEngine/ImbDataFlowManager.cpp: 708: ImbDataFlowManager::lockForUpdate: MessageFlow: 7c6f6c3b-1c01-0000-0080-804532efde2d

**********************************************************

BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1045I: Connecting to the Configuration Manager...
BIP1039I: Deploying BAR file 'D:\CVS_WORK\OffGenDeplCommand\Geneva\CORONA.bar' t
o broker 'BKDEV02' (execution group 'EGOTH03') ...
BIP1093E: Broker BKDEV02 reported the following error(s):
BIP2087E: Broker BKDEV02 was unable to process the internal configuration messag
e.

The entire internal configuration message failed to be processed successfully.

The internal configuration message failed to be processed, use the messages foll
owing this message to determine the reasons for the failure.
BIP4041E: Execution group 'EGOTH03' received an invalid configuration message. S
ee the following messages for details of the error.

The message broker received an invalid configuration message and has not updated
its configuration. This can arise as a result of errors in the specification o
f either message flows or message sets which the configuration manager was unabl
e to detect. It can also result from a message flow requiring a type of node th
at is not supported by the broker installation, from the broker having become ou
t of step with the configuration database or from other applications sending ext
raneous messages to the broker's configuration queues (SYSTEM.BROKER.ADMIN.QUEUE
& SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).

Check the relevant message flow and message set definitions, check that all nece
ssary user-defined extensions are installed, perform a complete redeploy of the
broker's configuration and ensure that no applications are writing to the broker
's configuration queues.
BIP2242E: Message flow 'MF_NXGCOR_ASSET_ACC_CMPY_BAL_PYMT' could not be reconfig
ured because it remained busy for longer than the timeout period of '300000'

A request to reconfigure the message flow 'MF_NXGCOR_ASSET_ACC_CMPY_BAL_PYMT' wa
s received but this could not be processed because it remained busy processing a
message for longer than the timeout specified.

This can be caused by the timeout being too short considering the complexity of
the flow and the size of the messages being processed. In such cases the timeout
should be increased. It can also be caused by message flows containing infinite
loops. In such cases the SQL should be corrected.

BIP1039I: Deploying BAR file 'D:\CVS_WORK\OffGenDeplCommand\Geneva\CORONA.bar' t
o broker 'BKDEV02' (execution group 'EGOTH03') ...
BIP1093E: Broker BKDEV02 reported the following error(s):
BIP2087E: Broker BKDEV02 was unable to process the internal configuration messag
e.

The entire internal configuration message failed to be processed successfully.

The internal configuration message failed to be processed, use the messages foll
owing this message to determine the reasons for the failure.
BIP2066E: Broker BKDEV02 (UUID 95ba2238-1c01-0000-0080-9bd46f518460) was unable
to retrieve an internal configuration response message for execution group 'EGOT
H03' within the 360 second Configuration Timeout.

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

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 execut
ion 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 compl
exity 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 configurat
ion 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 messag
e no longer occurs. Contact your IBM support center if you are unable to resolve
the problem.

D:\CVS_WORK\OffGenDeplCommand\Geneva>
_________________
WebSphere MQ, MB Support and Admin