Bug 978492
Summary: | ActiveMQ fix for memory leak | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Luke Meyer <lmeyer> |
Component: | Node | Assignee: | Jason DeTiberus <jdetiber> |
Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.2.0 | CC: | adellape, bleanhar, gpei, jdetiber |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-08-05 17:17:56 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 906885 |
Description
Luke Meyer
2013-06-26 17:37:56 UTC
Built activemq-5.8.0-1.redhat.60024.el6op, will be included in the next puddle built. 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. 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 |