Bug 978492 - ActiveMQ fix for memory leak
Summary: ActiveMQ fix for memory leak
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 1.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Jason DeTiberus
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks: 906885
TreeView+ depends on / blocked
 
Reported: 2013-06-26 17:37 UTC by Luke Meyer
Modified: 2017-03-08 17:35 UTC (History)
4 users (show)

Fixed In Version: activemq-5.8.0-1.redhat.60024.el6op
Doc Type: Bug Fix
Doc Text:
Due to a bug in ActiveMQ's memory management, memory leaks could require ActiveMQ to be restarted, most noticeably under heavy load. With this fix, ActiveMQ in OpenShift Enterprise has been upgraded to the latest stable release from JBoss AM-Q. As a result, ActiveMQ no longer suffers from memory leaks.
Clone Of:
Environment:
Last Closed: 2013-08-05 17:17:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1138 0 normal SHIPPED_LIVE OpenShift Enterprise 1.2.1 bug fix and enhancement update 2013-08-05 21:14:54 UTC

Description Luke Meyer 2013-06-26 17:37:56 UTC
Description of problem:
Although no Enterprise incidence of this has yet surfaced, there have been occurrences of a memory leak in Online ActiveMQ servers that appear to be related to https://issues.apache.org/jira/browse/AMQ-4319 and backported to 5.8.0.

Version-Release number of selected component (if applicable):
activemq-5.6.0-5.el6op

How reproducible:
So far, not at all.

Actual results:
ActiveMQ heap usage grows until OOME and restart, generally not failing over gracefully.

Expected results:
Heap usage does not increase out of proportion to existing storage/usage.

Comment 3 Jason DeTiberus 2013-07-12 17:16:09 UTC
Built activemq-5.8.0-1.redhat.60024.el6op, will be included in the next puddle built.

Comment 5 Gaoyun Pei 2013-07-16 02:28:28 UTC
The new puddle 2013-07-12 is using activemq-5.8.0-1.redhat.60024.el6op.x86_64.

In the beginning of testing, check the mem usage of activemq:
PID  USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                                                                                          
                                                                                             
4940 activemq  20   0 2501m 248m  12m S  3.0  6.5   1:24.97 java


After a round of acceptance testing, check the usage again:
PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND            
             
4940 activemq  20   0 3282m 257m  12m S  0.7  6.7   8:22.36 java               

ActiveMQ took proper usage of MEM during it's running, so move it to VERIFIED.

Comment 8 errata-xmlrpc 2013-08-05 17:17:56 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1138.html


Note You need to log in before you can comment on or make changes to this bug.