| Author |
Message
|
| dosttumhara1810 |
 Posted: Tue Jan 14, 2014 9:22 pm Post subject: Memory leaks |
 |
|
Voyager
Joined: 01 Dec 2010
Posts: 76
|
hi All,
I have an issue with memory leaks in my PRODUCTION servers. There are total 6 production servers and the traffic is load balanced by load balancer. The issue here is the memory used by the EG in all 6 server is different and in 4 server it is almost 3 times the other two which is worrying me. I want to know the methods by which i can check which interface or flow is leaking memory in the EG's on all 6 servers. Checking the mqsi.log will not help much i guess. Suggest few other ways as well whic hcan help me do analysis why the memory consumption is high(10GB on one server.) |
|
| Back to top |
|
 |
| dosttumhara1810 |
| Posted: Tue Jan 14, 2014 9:32 pm Post subject: |
|
|
Voyager
Joined: 01 Dec 2010
Posts: 76
|
| one more point to add is the my Execution group memory consumption is increasing daily on 4 servers only and stable on 2 servers.. |
|
| Back to top |
|
|
| dosttumhara1810 |
| Posted: Wed Jan 15, 2014 2:47 am Post subject: |
|
|
Voyager
Joined: 01 Dec 2010
Posts: 76
|
|
| Back to top |
|
|
| Esa |
| Posted: Wed Jan 15, 2014 2:53 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
If your process supports this kind of approach:
Create a new execution group on one of the problematic brokers and move there one flow from the ill-behaving eg. Monitor memory consumption. If the problem moved in the new eg with the flow, you have found the correct flow. Otherwise move it back and test another flow.
Someone else may know a better or faster way, I hope. |
|
| Back to top |
|
|
| dosttumhara1810 |
| Posted: Wed Jan 15, 2014 8:55 pm Post subject: |
|
|
Voyager
Joined: 01 Dec 2010
Posts: 76
|
| thanks for the response but cannot , since i have 130 + flows running. in on EG |
|
| Back to top |
|
|
| Esa |
| Posted: Wed Jan 15, 2014 11:23 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
With 130 flows in an EG, daily increase of allocated memory might still be just statistical fluctuation...
There are nodes that are known to have caused memory leaks on certain broker versions, for example HttpHeader node.
Please tell us your broker, MQ and OS versions.
Is there something that prevents you from running mqsireload daily on the execution groups? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jan 16, 2014 6:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Esa wrote: |
| Is there something that prevents you from running mqsireload daily on the execution groups? |
It could be the same thing that prevents me from running mqsireload daily; people using them! 
(130 flows in an EG would keep the OP down for a period of time potentially greater than the SLA involved)
There are other ways to find poorly performing / leaking message flows; the resource statistics are a good place to start & don't require new execution groups.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jan 16, 2014 7:56 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Transaction volume and message size affect memory of the Execution Group.
The Load Balancer is almost certainly not distrubuting the load EXACTLY the same across the Execution Groups when you factor in transactions of all the messages flows in that same execution group and the message sizes.
The memory footprint should be different between Brokers.
Having said that, you want to know if there is a leak situation, although if there was you would expect it to be leaking the same across all the instances.
Is the memory footprint on the higher ones stable, or is it continually climbing and never stops until you restart things?
I have the same question you do - is there a way to identify the memory footprint of individual flows in a shared execution group.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| aggarwal.intouch |
| Posted: Sun Jan 19, 2014 10:56 pm Post subject: Memory Leaks |
|
|
Acolyte
Joined: 30 May 2011
Posts: 56
Location: India
|
Although there is no process to find out memory leak in an execution group having multiple flows in it.
As an interim solution I can think of is to restart your execution groups at frequent intervals to prevent out-of-memory exceptions.
Refer the following post as well for some pointers:
http://www.mqseries.net/phpBB2/viewtopic.php?t=44898 |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jan 20, 2014 8:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| the resource statistics are a good place to start & don't require new execution groups. |
|
|
| Back to top |
|
|
|
|
