Bug 1108952 - OutOfMemoryError with large patches
Summary: OutOfMemoryError with large patches
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Patching
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ER9
: EAP 6.3.0
Assignee: Emanuel Muckenhuber
QA Contact: Jan Martiska
Russell Dickenson
Depends On:
TreeView+ depends on / blocked
Reported: 2014-06-13 00:29 UTC by James Livingston
Modified: 2018-12-06 16:50 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In Previous versions of JBoss EAP 6, attachment data passed from master to slave host controllers was read fully into memory. As a consequence, when installing large patches, an `OutOfMemoryError` may occur on child host controllers. This could occur when installing CP04 via the domain controller with the default memory settings. In this release of the product, attachments are saved to temporary files, so as to not consume excessive memory and `OutOfMemoryErrors` do not occur on child host controllers.
Clone Of:
Last Closed: 2014-08-06 14:38:41 UTC
Type: Bug

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 949923 None None None Never
Red Hat One Jira Issue Tracker WFLY-3359 Major Resolved Transferring an operation attachments to slaves may lead to an OOM 2017-07-11 02:18:19 UTC

Description James Livingston 2014-06-13 00:29:29 UTC
Due to WFLY-3359 you can run out of heap space on slave HCs when installing large patches from the DC. A patch slightly over 128mb will temporarily need 384mb of space as the backing byte array is resized, likely causing an OOME with the default -Xmx512m setting.

Comment 4 Emanuel Muckenhuber 2014-06-13 11:53:56 UTC
Maybe this should be ported back to 6.2.x though? I don't recall if that happened.

Comment 5 James Livingston 2014-06-15 22:26:48 UTC
It's not in 6.2.x currently

Comment 8 Martin Simka 2014-07-03 12:20:36 UTC
verified on EAP 6.3.0.ER8 but not during ER8 test cycle. BZ was moved to ON_QA after ER8 test cycle ended.

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