Bug 793827 (JBEPP-902) - OOM Issue when starting up with many pages
Summary: OOM Issue when starting up with many pages
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-902
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: unspecified
Version: 5.1.0.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.1.DEV01
Assignee: Thomas Heute
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-26 11:58 UTC by Thomas Heute
Modified: 2012-02-28 16:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-28 08:13:47 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-902 0 None None None Never

Description Thomas Heute 2011-04-26 11:58:02 UTC
project_key: JBEPP

Comment 1 Thomas Heute 2011-04-28 08:13:47 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.


Comment 2 Scott Mumford 2011-04-29 01:55:02 UTC
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?)


Comment 3 Scott Mumford 2011-05-03 04:45:32 UTC
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.


Comment 4 Scott Mumford 2011-05-04 04:19:17 UTC
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.



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