| Author |
Message
|
| Feysn |
 Posted: Mon Dec 06, 2004 1:11 am Post subject: More Dataflowengine.exe's than Executiongroups in the toolki |
 |
|
Apprentice
Joined: 04 Jun 2004
Posts: 33
Location: Wilrijk
|
Dear,
There are more dataflowengine's running on my broker machine than there are Execution groups in the toolkit. These are execution groups that were deleted. For one reason the dataflowengines remain active and the messageflows deployed to those are still up and running. Is there a possibility to delete those dataflowengines because I can't conrol them anymore
Thans |
|
| Back to top |
|
 |
| kirani |
| Posted: Mon Dec 06, 2004 1:50 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Please provide your environment details. Are you at the latest fixpack? Some people in this forum have seen this kind of behaviour before and I belive the problem was resolved after they applied the latest CSD (CSD4).
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| chenulu |
| Posted: Mon Dec 06, 2004 2:10 pm Post subject: |
|
|
Voyager
Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC
|
Hi Feysn,
This could happen if the EG was deleted from the toolkit and you do not get a successful response from the broker. The EG does not get cleaned up from BROKERAAEG table. The broker upon startup reads this table to start the EGs from this table.
If you issue an mqsibrowse BrokerName -t BROKERAAGE you will see the EGs that the broker thinks existing are displayed.
-- Chenulu |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Dec 06, 2004 3:05 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
How would one clean-up these?
Would complete deploy of the broker help?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| chenulu |
| Posted: Mon Dec 06, 2004 6:59 pm Post subject: |
|
|
Voyager
Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC
|
Hi,
This issue is currently being investigated and I will post the results once a resolution is found.
-- Chenulu |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Dec 06, 2004 11:48 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Is there any workaround for this problem?
I guess one of the workaround would be not to delete any EG after it's created??
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Feysn |
| Posted: Tue Dec 07, 2004 12:08 am Post subject: |
|
|
Apprentice
Joined: 04 Jun 2004
Posts: 33
Location: Wilrijk
|
Thanks for all the replies,
Indeed we are now at the CSD3 level. I will apply the CSD4 and come back with results. |
|
| Back to top |
|
|
| chenulu |
| Posted: Tue Dec 07, 2004 3:00 am Post subject: |
|
|
Voyager
Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC
|
Hi Kiran,
Regarding the workaround, this does not happen all the time from what I know. Ensure that you get a successful response from the broker (for the implicit deploy) when you delete any component.
-- Chenulu |
|
| Back to top |
|
|
| Feysn |
| Posted: Tue Dec 21, 2004 4:23 am Post subject: Solution |
|
|
Apprentice
Joined: 04 Jun 2004
Posts: 33
Location: Wilrijk
|
Dear all, who have helped me during this topic.
Solution for these problem is.
Stop the Broker
Delete in the Broker DB in the following tables the record with the ExecutionGroupUUID:
BRMINFO
BRMPHYSICALRES
BRMRTDDEPINFO
BRMRTDINFO
BRMWFDINFO
BROKERAAEG
BROKERRESOURCES
To determine the UUID for the Executiongroups you need the Windows Process ID in the case that you work on a windows machine. This can in an easy way be determined when the broker is running via the debugger. With the process ID you can find the UUID and with the UUID you can delete the records< |
|
| Back to top |
|
|
| kirani |
| Posted: Tue Dec 21, 2004 7:30 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Hmmm .. It's very dangerous to update Broker's Internal database manually.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Feysn |
| Posted: Wed Dec 22, 2004 12:00 am Post subject: |
|
|
Apprentice
Joined: 04 Jun 2004
Posts: 33
Location: Wilrijk
|
Sure Kiran it is dangerous to do. But sometimes this is the only solution. Because on CSD04 we had the same problem.
Because we are in a Hot-Failover/ Disaster Setup we can't recreate the broker as IBM proposed to us. |
|
| Back to top |
|
|
|
|
