| Author |
Message
|
| prat31 |
 Posted: Wed Sep 18, 2013 8:22 am Post subject: |
 |
|
Apprentice
Joined: 01 Feb 2013
Posts: 30
|
Dear Mr. Vitor,
We applied the mqsichangebroker command to 8.0.0.2.. Now the effective level is showing 8.0.0.2.. but the problem still persists.. We restarted the broker and still the duplicate DFE are creating... |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Sep 18, 2013 9:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| prat31 wrote: |
| We restarted the broker and still the duplicate DFE are creating... |
You need to search this forum and/or raise a PMR for this situation, known to most as "phantom execution groups". The broker registry is corrupt and needs to be fixed. Carefully.
Or delete & recreate the broker.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| prat31 |
| Posted: Wed Sep 18, 2013 9:50 am Post subject: |
|
|
Apprentice
Joined: 01 Feb 2013
Posts: 30
|
if we clear logs under /var/mqsi/common/locks , will it help to resolve this issue?
there are files named with the broker... |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Sep 18, 2013 9:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| prat31 wrote: |
| if we clear logs under /var/mqsi/common/locks , will it help to resolve this issue? |
No. Those are used for something else.
Do not start randomly deleting stuff under /var/mqsi in the hopes it will help. Either search the forum for procedures people have used or (better still) raise a PMR and get assistance.
If you're prepared to pick victims under /var/mqsi to delete, consider deleting and recreating the broker instead. Because one false move & you'll need to do that anyway!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| prat31 |
| Posted: Thu Sep 19, 2013 4:38 am Post subject: |
|
|
Apprentice
Joined: 01 Feb 2013
Posts: 30
|
| Thanks for the inputs. We just restore the data from the backup and issue resolved. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 19, 2013 4:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| prat31 wrote: |
| We just restore the data from the backup and issue resolved. |
Which is deleting and recreating the broker; you're deleting the corrupt one and replacing it with a working copy. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Sep 19, 2013 5:05 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| prat31 wrote: |
| Thanks for the inputs. We just restore the data from the backup and issue resolved. |
What 'data' did you restore? One file? One dir? The entire server?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| prat31 |
| Posted: Thu Sep 19, 2013 8:28 am Post subject: |
|
|
Apprentice
Joined: 01 Feb 2013
Posts: 30
|
Hi Peter,
we have restored 2 folders, /var/mqsi/registry/Brokername and /var/mqsi/components/Brokername.
thanks for all your inputs. |
|
| Back to top |
|
|
| prat31 |
| Posted: Sat Sep 21, 2013 12:22 am Post subject: |
|
|
Apprentice
Joined: 01 Feb 2013
Posts: 30
|
Hi All,
We were again getting the duplicate DataFlowEngines and /opt/IBM/mqsi/8.0.0.2/bin/startDataFlowEngine for EGs.
The broker points to the Fix Pack 8.0.0.2. Request you to let us know the solution to overcome the duplicates as because of this the flows in EG are showing running but they are not processing the inputs and IPPROCS of queue is shown as 0.
Thanks.. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Sep 21, 2013 12:58 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Perhaps it is time to raise a PMR?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Sep 21, 2013 8:06 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| prat31 wrote: |
Hi All,
We were again getting the duplicate DataFlowEngines and /opt/IBM/mqsi/8.0.0.2/bin/startDataFlowEngine for EGs.
The broker points to the Fix Pack 8.0.0.2. Request you to let us know the solution to overcome the duplicates as because of this the flows in EG are showing running but they are not processing the inputs and IPPROCS of queue is shown as 0.
Thanks.. |
AFAIK this is standard behavior in V8. The startDataFlowEngine is a minor process that will verify that the DataflowEngine is running and spawn a new one if it does not.
However you should open a PMR to get this behavior confirmed.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| prat31 |
| Posted: Sun Sep 22, 2013 8:22 am Post subject: |
|
|
Apprentice
Joined: 01 Feb 2013
Posts: 30
|
Hi all,
To add to the above.. We are getting the duplicates when we are killing the broker processes when it does not stop using commands... |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Sep 23, 2013 3:03 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| karthik_ps |
| Posted: Thu Sep 26, 2013 4:36 am Post subject: |
|
|
Apprentice
Joined: 10 Dec 2008
Posts: 43
|
Hi lancelotlinc,
we are using common user called mbid to perform MQ and MB administration. i have raised PMR with IBM and below is the link shared by them.
http://www-01.ibm.com/support/docview.wss?uid=swg21587240
From their point of view, broker process should not be killed. if it takes hours to stop, we have to wait for it.
Note : myself and pratik are working in the same team. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Sep 26, 2013 5:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The thing you need to DETERMINE is why the DFE is not stopping.
This is almost always the result of a STUCK MESSAGE FLOW.
Which is almost always a result of BAD CODING.
Take a user trace of the EG, let it run for about 2 minutes.
Look to see what flows are running in a loop. |
|
| Back to top |
|
|
|
|
