| Author |
Message
|
| mangoMan |
 Posted: Tue Sep 07, 2004 8:44 am Post subject: Unable To Deploy MsgFlow |
 |
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
Ok I give up. I have tried everything and nothing seems to work.
Here is what is happening:
1. I deploy a bar file.
2. I wait and wait and wait
3. I get the following 2 messages in the WMQ event log
| Quote: |
BIP2087E: Broker TEST_BROKER was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
The internal configuration message failed to be processed, use the messages following this message to determine the reasons for the failure.
|
| Quote: |
BIP2066E: Broker TEST_BROKER (UUID d79ce1c0-fe00-0000-0080-bc8b46d8ed36) was unable to retrieve an internal configuration response message for execution group 'default' 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 MQ 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. 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.
|
4. I see that there is a message sitting on the SYSTEM.BROKER.EXECUTIONGROUP.QUEUE queue.
5. I deploy again and the same thing happens and I see another msg pile up on SYSTEM.BROKER.EXECUTIONGROUP.QUEUE
6. I have deleted the broker and the config manager but have had no luck. I get the same errors again.
7. Any ideas? |
|
| Back to top |
|
 |
| PGoodhart |
| Posted: Tue Sep 07, 2004 9:08 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
If you are not using the same queue manager for both, you must have a good connection between your broker machine and your configuration manager. This means good channels, and transmission queues.
Secondly this can occur when the user ids permissions are not properly set. (You have to have the right groups associated with the user ids the tools run under. Are you a member of MQM?)
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| mangoMan |
| Posted: Tue Sep 07, 2004 2:09 pm Post subject: |
|
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
| Yes I am running the broker and the config mgr on the same box so there should be no issues with communication. I both the usernames I am using are under all the wbi groups and mqm. |
|
| Back to top |
|
|
| JT |
| Posted: Tue Sep 07, 2004 7:01 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
|
| Back to top |
|
|
| mangoMan |
| Posted: Wed Sep 08, 2004 7:00 am Post subject: |
|
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
Thanks everyone for your help.
I am able to deploy now. I had to use the following command to increase broker timeout interval:
| Quote: |
mqsichangebroker <BROOKERNAME> -a userID -i Password -g 1000 -k 1000
|
I don't know why but it takes for ever to deploy in my laptop. Around 10 minutes. I have 1 gig of RAM and I have ordered another gig hoping that extra RAM will fix this. |
|
| Back to top |
|
|
| PGoodhart |
| Posted: Wed Sep 08, 2004 9:15 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
If you are using version 5 you might want to start with a fresh bar file.
If you keep editing a bar file it gets very large, and then you have deployment problems. You might want to see if you have a very large message set too. I had someone import a schema that was almost a gig with all the references. It had about a hundred different complex message types, but we never used more then two.
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
|
|
