| Author |
Message
|
| VishnuPrasadS |
 Posted: Thu Nov 07, 2013 10:25 pm Post subject: Unable to delete execution_group |
 |
|
Apprentice
Joined: 22 Feb 2013
Posts: 28
Location: Pune, India
|
Hi
Unable to delete execution_group
EG's are visible through "mb toolkit","mqsilist command","cmp api".
But actions on eg such as delete,rename dont take effect.
Iam able to stop the eg to stop log entry listed below.
Message: BIP2880I
Source: Change Notification
Creation time: {time_stamp}
BIP2880I: The property 'processId' has changed from '52494344' to '52494346' on object '{execution_group_name}' of type 'ExecutionGroup' with parent {broker_name} of type 'Broker'.
This occurs repeatedly in approximate interval of 1 min
{} symbol used to indicate edits I made to log
Awaiting your suggestions |
|
| Back to top |
|
 |
| VishnuPrasadS |
| Posted: Thu Nov 07, 2013 11:55 pm Post subject: Update |
|
|
Apprentice
Joined: 22 Feb 2013
Posts: 28
Location: Pune, India
|
I was able rename eg. Initially it returned timeout after 360 seconds. But after some time, i could see eg's name was changed.
Disabling debug port, deleting eg are not possible.(Result in timeout)
Environment details
MB version : 7.0.0.5
MQ version : 7.0.1.8
OS : AIX
Article i found with similar issue;
Below suggestions are not applicable to my issue as
1. my mb version is not 6.
2. eg jvmDebugPort is 5142
Article 1 ...
For MB6
1. Go to the broker database
2. Locate BROKERAAEG table
3. Delete the row where PROCESSID = the Windows processid under Task Manager
4. Do deploy Topology Configuration -> complete
5. MQSISTOP broker
6. MQSISTART broker
7. MQSILIST broker. The execution group should disappear
8. Count the number of Dataflowengines in Task Manager
9. Count the number of execution groups in WBIMB
10. If 8. and 9. are the same, it works !
11. Otherwise, find another medieval method.
Article 2 ...
For the case where the debug port is < 1024, or any port lower than 1024, try the following:
add root to the mqbrkrs group
start the broker with root
change the port to a number > 1024 using root to do it
bounce the broker twice (using root)
stop the broker
remove root from mqbrkrs group
start broker with normal (service) id |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Nov 08, 2013 8:06 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Tell the EG to delete all flows and resources.
Manually kill the EG process.
Wait for it to restart and process the delete flows and resources command. |
|
| Back to top |
|
|
| VishnuPrasadS |
| Posted: Sat Nov 09, 2013 3:09 am Post subject: |
|
|
Apprentice
Joined: 22 Feb 2013
Posts: 28
Location: Pune, India
|
|
| Back to top |
|
|
| Tibor |
| Posted: Sat Nov 09, 2013 4:29 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| In WMB v7 there is no configuration database, you can change almost *any* settings in the filesystem under $MQSI_WORKPATH/registry, default is /var/mqsi/registry. So you can increase the timeout values, too. |
|
| Back to top |
|
|
| VishnuPrasadS |
| Posted: Sat Nov 09, 2013 5:35 am Post subject: |
|
|
Apprentice
Joined: 22 Feb 2013
Posts: 28
Location: Pune, India
|
Hi Tibor
--> changed ConfigurationTimeout to 600 from 300 in /var/mqsi/registry/{broker_name}/CurrentVersion
--> did broker reload ( mqsistop {broker_name}, mqsistart {broker_name} )
--> problem still remains
BIP2066E: Broker '{broker_name}' was unable to retrieve an internal configuration response message for execution group '{eg_name}' within the '660' second configuration timeout.
Below url has broker administration log which can explain the sequence of events that occured
https://drive.google.com/file/d/0Bz3bVRRIu-RVZFQtRzBrWlRTRVU/edit?usp=sharing |
|
| Back to top |
|
|
| Tibor |
| Posted: Sat Nov 09, 2013 5:50 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| Hi VishnuPrasadS, I know it is not officially supported, but (after creating a backup of your $MQSI_WORKPATH) you can try simply remove all the execution group directories, identified by its UUID under $MQSI_WORKPATH/components and $MQSI_WORKPATH/registry. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Nov 09, 2013 1:31 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
disable all inputs to the e.g.
send the e.g. stop command.
kill the e.g. process
remove all deployed flows.
delete e.g.
create e.g. with new name
deploy code (you need to modify it and find the endless loop and kill that one)
restart all.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| VishnuPrasadS |
| Posted: Sat Nov 09, 2013 9:00 pm Post subject: |
|
|
Apprentice
Joined: 22 Feb 2013
Posts: 28
Location: Pune, India
|
Hi Tibor
$MQSI_WORKPATH/components will have folders with egUUID as name which we can remove,
But what to delete from $MQSI_WORKPATH/registry ?
--------------------------------------
Hi fjb_saper
--> all inputs to eg were disabled few days ago.
--> eg is currently in stopped mode.
--> as the eg is in stopped mode, process id will be 0(no process exists), and hence cannot kill it.
--> after stopping the eg, "remove all deployed flows" or "delete eg" commands cannot be issued. |
|
| Back to top |
|
|
| Tibor |
| Posted: Sun Nov 10, 2013 12:30 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| I have such a feeling, both of your posts have same root: mismatching v6 and v7 instances under an identical $MQSI_WORKPATH. Is it true? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Nov 10, 2013 10:21 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Tibor wrote: |
| I have such a feeling, both of your posts have same root: mismatching v6 and v7 instances under an identical $MQSI_WORKPATH. Is it true? |
Tibor, I had no problem running a V6.0 and a V7 broker under the same workpath (before 6.0 ran out of support), however I had to use different service user (userid) for each. It is important that the login script define the correct environment (via mqsiprofile) so that there is no environment leakage between the different versions.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Tibor |
| Posted: Mon Nov 11, 2013 1:09 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
Hi fjb_saper, you would be right, maybe I was not brave enough for mixing versions  |
|
| Back to top |
|
|
| VishnuPrasadS |
| Posted: Sun Feb 01, 2015 8:36 am Post subject: solution |
|
|
Apprentice
Joined: 22 Feb 2013
Posts: 28
Location: Pune, India
|
Hello All,
I was revisiting my old post and decided to add any new data I since had.
Problem : Unable to delete execution group.
Reason : Execution group's jvm debug listener was enabled with a port which was currently in use by another process.
Solution : Make this port available by stopping the other process. Then issue delete command to 'EG'. |
|
| Back to top |
|
|
|
|
