| Author |
Message
|
| essive |
 Posted: Mon May 02, 2005 1:37 pm Post subject: Odd Broker Execution Group name after mqsistart |
 |
|
Novice
Joined: 15 Nov 2004
Posts: 24
|
Has anyone ever seen this before on a new Message Broker install? This is on a Solaris 9 server.
wbrkadm 4076 4073 0 16:22:58 ? 0:06 DataFlowEngine TSTBK1 82A6E590-12B3-11D3-81A2-00203506A68E $SYS_mqsi 1
Look at the DataFlowEngine name '$SYS_mqsi'. It should say 'default'. Our other servers installed correctly. That looks like an environment variable. The logs say successful start. We've tried copying profiles from other servers and recreating the broker but keep getting this weird DataFlowEngine and cannot deploy any flows.
Message Broker 5.0 FP4 |
|
| Back to top |
|
 |
| JT |
| Posted: Mon May 02, 2005 1:57 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| When you first deploy to a broker, you might not be deploying to an execution group. This is the case if you select topology deploys. The result of this type of deployment is a process that is labelled $SYS_mqsi. This process is used to handle publish/subscribe data. If you successfully deploy other execution groups to the broker, the $SYS_mqsi process is not started; its role is taken by one of the running execution groups. |
|
|
| Back to top |
|
|
| essive |
| Posted: Tue May 03, 2005 6:41 am Post subject: |
|
|
Novice
Joined: 15 Nov 2004
Posts: 24
|
That may be true - however, if we create a new exection group we still cannot deploy to it. Also, the Broker Admin screen has Alerts that the broker is not running and the Execution Groups are not as well.
We are going to completely re-install. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue May 03, 2005 6:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| essive wrote: |
That may be true - however, if we create a new exection group we still cannot deploy to it. Also, the Broker Admin screen has Alerts that the broker is not running and the Execution Groups are not as well.
We are going to completely re-install. |
Don't.
The alerts are normal.
What error do you get if you try to deploy?
Did you deploy the Topology first?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sysalley |
| Posted: Thu May 05, 2005 7:49 pm Post subject: |
|
|
Newbie
Joined: 27 Apr 2005
Posts: 4
|
I also have the same problem there is a alert Execution Group is not running.
and I can deploy message flow with no error but as there is alert in execution group so it dont show the mesg flow.
pls. advice how to resolve this issue |
|
| Back to top |
|
|
| sysalley |
| Posted: Thu May 05, 2005 8:20 pm Post subject: error is below |
|
|
Newbie
Joined: 27 Apr 2005
Posts: 4
|
BIP2066E: Broker TBRK_BROKER (UUID de1a6ba6-0301-0000-0080-bd71b17ccb32) was unable to retrieve an internal configuration response message for execution group 'wbimbadm' 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. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri May 06, 2005 3:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You don't have good commmunications between the broker hosting that eg and the config mgr.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| waugh |
| Posted: Fri May 06, 2005 5:33 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
$SYS_mqsi is normal, when your very first deployment to the broker goes successful, it will be replaced by 'default' exceution group.
As Jeff mentioned it might be a communication issue between your config and broker. make sure your channels are up between config and broker QM'S and try increasing the timeout period on configmgr to see if that helps. also does that user running toolkit has right permissions on config? |
|
| Back to top |
|
|
| essive |
| Posted: Fri May 06, 2005 8:45 am Post subject: |
|
|
Novice
Joined: 15 Nov 2004
Posts: 24
|
| They are all correct. It turned out to be the channels between the Config Mgr QM and the Broker QM had dropped. That fixed the problem and all other comments above are correct. |
|
| Back to top |
|
|
|
|
