| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP2066E_Broker Issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| pbravic |
 Posted: Mon Nov 24, 2003 11:28 am Post subject: BIP2066E_Broker Issue |
 |
|
Apprentice
Joined: 24 Nov 2003
Posts: 42
|
Hi
our MQSI Version is 2.02, db2 version 7.1 (no fixpack) and MQSeries 5.2.1 (CSD05).
This is the initial setup, we started setting up the same for the testing environment. All Message flows were working fine.
When we installed WMQSI CSD03 (U200172) to have the environment same as that of production (db2 and mqseries are same as that of production). when tested No message flow is working. All messages are in the input queues.
After redeploying we were not able to bringdown the Broker using mqsistop command (we need to use force stopping by mqsistop -i).
after restarting the broker and redeploying we are getting the below messages
I had increased the db2heapsize to 1000 and application heapsize to 1024 as earlier told in this forum and MQSeries log is also increased
Error we are getting
-----------------------
BIP2066E: Broker BRK1 (UUID 05d0e506-f900-0000-0080-d18fcd6d4412) unable to retrieve internal configuration response message for execution group default.
The execution group did not respond in a timely manner. The internal configuration message response will be discarded if it arrives after this point.
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 MQSeries 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 Control Center. Contact your IBM support center if you are unable to resolve the problem.
----------------------
Pls do let me know your inputs for solving the same
Thanks in Advance
Thanks and Regards
ravichandran |
|
| Back to top |
|
 |
| asamanta |
| Posted: Mon Nov 24, 2003 9:50 pm Post subject: |
|
|
Novice
Joined: 20 Aug 2003
Posts: 18
|
After install the CSD, you need to delete the configmgr and re-create the configmgr again. Now, you import your mesage flow and deploy in the broker
Hope, this will solve your problem..
Ardh |
|
| Back to top |
|
|
| vignesh.gopal |
| Posted: Mon Nov 24, 2003 11:24 pm Post subject: Broker Issue |
|
|
Novice
Joined: 23 Dec 2002
Posts: 24
|
Hi ,
This is becos the configuration details are not being updated within the timeout value set by default.
To achieve this status please foloow the below mentioned details and change the values in the broker using the mqsichangebroker.
mqsichangebroker <BROOKERNAME> -a userID -i Password -g 200 -k 300
You can configure the time taken to regain control of the system following a stall
to reduce the effect on message flow performance. You can use the parameters
ConfigurationTimeout and ConfigurationDelayTimeout on the commands
-g ConfigurationTimeout
It is the time (in seconds) that an execution group in the broker is
allowed to take to apply a change in configuration
-k ConfigurationDelayTimeout
It is the time (in seconds) that a broker is allowed to take to
process a minimal change in configuration
U can also try this after recreating the configmgr ,but these would only hamper with certain properties which you will come across in the Promote Property values in the Input Node.
Thanks & regards
Vignesh |
|
| 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
|
|
|
|
