| Author |
Message
|
| rahuldhanpal |
 Posted: Fri Jun 17, 2011 4:30 am Post subject: Duplicate EG Processes |
 |
|
Voyager
Joined: 24 Jan 2009
Posts: 84
Location: Kenosha WI
|
Guys,
I have an issue with the EG processes running on a Broker V7.0.0.1 on RHEL
i see duplicate proccesses of each EG running and i get conflicts with some deployments i do. i tried stopping broker and the command returns successfully but i see the duplicate processes hanging around and i have to kill them manually and not sure why this is happening. here is a snapshot from the process status and this is what i see
wbrkadm 27857 1 0 Jun16 ? 00:00:05 DataFlowEngine BROKER af8f7782-2e01-0000-0080-9b726dd80f93 EG1
wbrkadm 27858 1 0 Jun16 ? 00:00:38 DataFlowEngine BROKER bd0d7782-2e01-0000-0080-9b726dd80f93 EG2
wbrkadm 27859 1 0 Jun16 ? 00:00:08 DataFlowEngine BROKER f79f7682-2e01-0000-0080-9b726dd80f93 EG3
wbrkadm 27994 27861 0 Jun16 ? 00:00:05 DataFlowEngine BROKER af8f7782-2e01-0000-0080-9b726dd80f93 EG1
wbrkadm 27995 27861 0 Jun16 ? 00:00:20 DataFlowEngine BROKER aa2b7882-2e01-0000-0080-9b726dd80f93 EG4
wbrkadm 27996 27861 0 Jun16 ? 00:00:24 DataFlowEngine BROKER bd0d7782-2e01-0000-0080-9b726dd80f93 EG2
wbrkadm 27997 27861 0 Jun16 ? 00:00:08 DataFlowEngine BROKER f79f7682-2e01-0000-0080-9b726dd80f93 EG3
Any pointers highly appreciated... please let me know if i dint make myself clear. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Jun 17, 2011 4:39 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
The first three seem to be 'orphaned' from the bipbroker/bipservice processes.
Do the logs show any EG Crashes/restarts?
Which version/patch level of RHEL are you on?
_________________
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 |
|
|
| mqjeff |
| Posted: Fri Jun 17, 2011 4:47 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Are you sure you aren't confusing threads with processes?
When mqsistop "returns successfully", does the log show that the broker has fully shut down? |
|
| Back to top |
|
|
| rahuldhanpal |
| Posted: Fri Jun 17, 2011 5:01 am Post subject: |
|
|
Voyager
Joined: 24 Jan 2009
Posts: 84
Location: Kenosha WI
|
@smdavies: no broker log does not show any crashes. but when i stop the broker it says all the processes shut down normally but i see the orphaned processes running and i have to kill them manually. and when i start the broker after examining if all the http/https ports are released correctly then i see couple of pids followed by theexecution group process dint not shutdown and also says the soap port is still in use.
we are at RHEL V5.4
@mqjeff: yes the log shows the broker shut down normally but as said the duplicate processes still hang around  |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jun 17, 2011 5:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Do you have code in your message flows that uses Java and does anything to create threads?
Does the issue always happen with the same EGs? If you delete and recreate those EGs does it happen again? |
|
| Back to top |
|
|
| rahuldhanpal |
| Posted: Fri Jun 17, 2011 5:27 am Post subject: |
|
|
Voyager
Joined: 24 Jan 2009
Posts: 84
Location: Kenosha WI
|
| mqjeff wrote: |
| Do you have code in your message flows that uses Java and does anything to create threads? |
yes we have couple of msg flows using java and also have some jars deployed but only on 1 EG and not on all of them and we have additional instances(9 threads) of some of the message flows running whcih is also for 1 one of the execution groups
| mqjeff wrote: |
| Does the issue always happen with the same EGs? If you delete and recreate those EGs does it happen again? |
yes this happens with the same execution groups and we never tried recreating the EG's coz there are bunch of message flows in there.
And another point to mention is this is one of the active broker instance and we have another active broker running on another server which works fine and does not show any such kind of behavior.
Thanks
RD |
|
| Back to top |
|
|
| mqjava |
| Posted: Wed Jun 22, 2011 11:41 am Post subject: |
|
|
Voyager
Joined: 25 May 2009
Posts: 80
Location: New Jersey
|
same behavoiur on our environment too .. did you find any solution for this?
Environment:
MB 7001 on RHEL 5.3
Thanks. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jun 22, 2011 11:47 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
This happens on Windows also.
For RHEL, I found the culprit to be lack of following the Chapter Six installation steps exactly as defined step-by-step. It relates to the service ID being used to start broker is not mqbrkrs; or the service ID does not have the same priv's as mqbrkrs ID; or the ownership of the files in /opt/mqsi is incorrect; or the ownership of the files in $MQSI_WORKPATH is incorrect.
The step-by-step instructions call for creating the group ID first, then the service ID next. To mqsistart the broker, you need to sudo into the mqbrkrs service ID. If you do not, you end up with orphaned DataFlowEngine processes.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjava |
| Posted: Thu Jun 23, 2011 5:57 am Post subject: |
|
|
Voyager
Joined: 25 May 2009
Posts: 80
Location: New Jersey
|
Thanks for the reply lancelotlinc.
Looks like all the settings mentioned in the chapter 6 are done, but in our environment we start the broker as Queue Manager service .. Queu manager runs on broker's service id, but we start the service from our own id, our own id's are part of mqm group.
Do you think starting the broker as service from other id is the problem here? but i see broker's process running in broker's service id when i start it as a service from other id.
If we have to start the broker as service can you please let me know the correct way of doing it.
Thanks in advance. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Jun 23, 2011 6:13 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
You can do it anyway you want, but if you having trouble, I think doing it a different way is a good way to troubleshoot to resolve the problem.
On my RHEL instances, I define a startup script that kicks off the broker at boot time. In this script, I sudo into mqbrkrs id to run mqsistart.
If I want to stop and start a broker, I always sudo into mqbrkrs id to do it. Starting broker uunder one id, then trying to stop broker from a different id usually hangs the DataFlowEngine processes even if both are in mqbrkrs group.
You may want to check your file ownerships also. If you or your system admin ran the install script before creating the group id and the service id, then the files are all owned by the wrong user id with the wrong group permissions.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjava |
| Posted: Fri Jun 24, 2011 6:33 am Post subject: |
|
|
Voyager
Joined: 25 May 2009
Posts: 80
Location: New Jersey
|
| ok .. will check the file permissions, we have the multi instance broker thats the reason we wanted the broker to start as the qmgr service, is there any other way to start the broker when using multi instance configuration. Thanks for your reply. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Jun 24, 2011 7:03 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| mqjava wrote: |
| ok .. will check the file permissions, we have the multi instance broker thats the reason we wanted the broker to start as the qmgr service, is there any other way to start the broker when using multi instance configuration. Thanks for your reply. |
Multi instance broker = yukky. Use multiple single instance brokers instead. More bang for the buck.
Also, on RHEL, I've noticed if the service id's primary group is not mqbrkrs, you have same issue. It's not enough to be a member of the mqbrkrs group, the service id's primary group must be mqbrkrs.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jun 24, 2011 7:16 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| Multi instance broker = yukky. Use multiple single instance brokers instead. More bang for the buck. |
Active / Active! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Jun 24, 2011 7:26 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Vitor wrote: |
| lancelotlinc wrote: |
| Multi instance broker = yukky. Use multiple single instance brokers instead. More bang for the buck. |
Active / Active! |
ABSOLUTELY RIGHT! I like the effect that Jolt cola and Pepperoni Pizza has on your personality Sir Vitor.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jun 24, 2011 7:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| ABSOLUTELY RIGHT! I like the effect that Jolt cola and Pepperoni Pizza has on your personality Sir Vitor. |
What? That it enables me to notice you're still pushing this viewpoint as an absolute truth even though it's an opinion much debated? That even your "more bang for the buck" comment glosses over the fact that multiple single brokers involves more buck?
And most importantly of all, ignores the fact that the OP is asking for help with the setup he's been asked to get working & doesn't need to be told he's doing it wrong? Even if we accept he is? Which we don't?
Because once again I point out that unlike in your world, most situations don't allow for a change of direction mid-flow. Especially if it costs money.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
