|Summary:||OutOfMemoryError with large patches|
|Product:||[JBoss] JBoss Enterprise Application Platform 6||Reporter:||James Livingston <jlivings>|
|Component:||Patching||Assignee:||Emanuel Muckenhuber <emuckenh>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||Jan Martiska <jmartisk>|
|Severity:||high||Docs Contact:||Russell Dickenson <rdickens>|
|Version:||6.2.0||CC:||dandread, jason.greene, jawilson, jdoyle, jlee, joallen, kconner, msimka, olubyans, schaudha, smumford|
|Target Release:||EAP 6.3.0|
|Fixed In Version:||Doc Type:||Bug Fix|
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.
|Last Closed:||2014-08-06 14:38:41 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
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.