Bug 779577 (SOA-1952) - SOA-P memory settings should be inherited from EAP
Summary: SOA-P memory settings should be inherited from EAP
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1952
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EAP, Build Process
Version: 5.0.0 CR1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.0.0 GA
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-17 11:39 UTC by Martin Vecera
Modified: 2010-02-19 16:05 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-19 16:05:21 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779317 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Issue Tracker SOA-1952 0 None None None Never

Internal Links: 779317

Description Martin Vecera 2010-02-17 11:39:41 UTC 
Date of First Response: 2010-02-17 15:50:16
project_key: SOA

Dominik Pospisil mentioned to us that the SOA-P memory settings passed to JVM uses less mem. for heap than EAP. This is a problem because EAP itself has problems with such low memory. We should inherit the Xms and Xmx settings from EAP. PermSize can be bigger for SOA-P.
Comment 1 Martin Vecera 2010-02-17 11:39:58 UTC 
Link: Added: This issue is related to SOA-1705
Comment 2 Len DiMaggio 2010-02-17 20:50:16 UTC 
It looks like there was a similar problem in EAP 4 - JBPAPP-2847

That is also in EAP 5.   JBPAPP-3763
Comment 3 Len DiMaggio 2010-02-17 20:51:08 UTC 
Link: Added: This issue depends JBPAPP-3763
Comment 4 Len DiMaggio 2010-02-19 16:05:21 UTC 
Verified in GA build.
Note You need to log in before you can comment on or make changes to this bug.