| Summary: | OOM Issue when starting up with many pages | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Thomas Heute <theute> |
| Component: | unspecified | Assignee: | Thomas Heute <theute> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.1.0.GA | CC: | epp-bugs |
| Target Milestone: | --- | ||
| Target Release: | 5.1.1.DEV01 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBEPP-902 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-04-28 08:13:47 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: | |
|
Description
Thomas Heute
2011-04-26 11:58:02 UTC
Release Notes Docs Status: Added: Documented as Resolved Issue Release Notes Text: Added: An out of memory error could happen when trying to start with many pages defined in the XML descriptors. A transaction has been split so that all definitions of pages are not hold in memory before being written. Release Notes Docs Status: Removed: Documented as Resolved Issue Added: Needs More Info Release Notes Text: Removed: An out of memory error could happen when trying to start with many pages defined in the XML descriptors. A transaction has been split so that all definitions of pages are not hold in memory before being written. Added: Cause: In previous Portal versions, page definitions were held in system memory before being written when starting the Portal. Consequence: This could cause an Out Of Memory error if a large number of pages were defined in the XML descriptors (NEEDINFO How many is 'many' pages?). Fix: The transaction has now been split so that not all page definitions are held in memory prior to being written. Result: The Out Of Memory error is no longer encountered (NEEDINFO No upper limit on page numbers now?) Release Notes Docs Status: Removed: Needs More Info Added: Documented as Resolved Issue Release Notes Text: Removed: Cause: In previous Portal versions, page definitions were held in system memory before being written when starting the Portal. Consequence: This could cause an Out Of Memory error if a large number of pages were defined in the XML descriptors (NEEDINFO How many is 'many' pages?). Fix: The transaction has now been split so that not all page definitions are held in memory prior to being written. Result: The Out Of Memory error is no longer encountered (NEEDINFO No upper limit on page numbers now?) Added: Cause: In previous Portal versions, page definitions were held in system memory before being written when starting the Portal. Consequence: This could cause an Out Of Memory error if a large number of pages were defined in the XML descriptors. Fix: The transaction has now been split so that not all page definitions are held in memory prior to being written. Result: The Out Of Memory error is no longer encountered. Release Notes Text: Removed: Cause: In previous Portal versions, page definitions were held in system memory before being written when starting the Portal. Consequence: This could cause an Out Of Memory error if a large number of pages were defined in the XML descriptors. Fix: The transaction has now been split so that not all page definitions are held in memory prior to being written. Result: The Out Of Memory error is no longer encountered. Added: In previous Portal versions, page definitions were held in system memory before being written when starting the Portal. This could cause an Out Of Memory error if a large number of pages were defined in the XML descriptors. The transaction has now been split so that not all page definitions are held in memory prior to being written and the Out Of Memory error is no longer encountered. |