| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| No 'default' Execution Group running on Broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| TonyD |
 Posted: Wed Oct 15, 2008 3:45 pm Post subject: No 'default' Execution Group running on Broker |
 |
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
We have a broker configuration (CM and Broker) running on the same Linux machine, each with its own QM. The CM shows three execution groups (Toolkit Broker Admin and also CM Proxy API Exerciser); they are 'default' and two application execution groups 'egCMS01' and egCMS_Util'. However on the broker mqsilist lists 'egCMS01' only.
It would appear that the CM and Broker have got out of step somehow. In the CM proxy display the 'isDeployed()' and 'isRunning' property values for both 'default' and 'egCMS_Util' are 'false', while they are 'true' for CMS01'.
I am particularly surprised that the broker has no'default' execution group. This is a broker that has been around for a while.
A 'complete' topology deploy has no effect. The broker starts a 'default' execution group but then stops it.
I am thinking that the best approach will be to delete/recreate the broker. Has anyone seen similar behaviour, and if so, worked out how the situation occurred? |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Oct 15, 2008 7:24 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
deploy some couple of flows to default and lets see if its getting displayed, or did you see any errors in the system logs
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| mqmatt |
| Posted: Thu Oct 16, 2008 3:12 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Tony,
That's what I'd expect to see if you'd just created the other two execution groups in the Toolkit, but you'd never deployed anything to them.
As Gaya3 suggests, deploy message flows to them and they should appear on the broker machine.
Cheers
-Matt
Edit: The default execution group needn't necessarily be called 'default'. I wouldn't worry about not seeing this execution group, unless the broker's reported errors in the syslog. |
|
| Back to top |
|
|
| TonyD |
| Posted: Thu Oct 16, 2008 11:32 am Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
I had tried to deploy to both execution groups, both of which had what appear to be valid folders for their UUIDs under the ../Components folder. However the messages just sat on SYSTEM.BROKER.EXECUTIONGROUP.QUEUE. Also getting the ' ... failed to get response ...' configuration timeout messages in the log, and 'unreadable' replies coming back to the CM .
I then deployed a flow to 'egCMS01'; it shows under mqsilist in the execution group, but not in the Toolkit Broker Admin view!
Not a good state of affairs!
Thanks for the comments. |
|
| 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
|
|
|
|
