Bug 777760 (SOA-276) - permgen space too low
Summary: permgen space too low
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-276
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Configuration
Version: 4.2 Beta 1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 Beta 2
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-04 18:55 UTC by Aleksandar Kostadinov
Modified: 2008-01-23 08:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-23 08:57:49 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 Issue Tracker SOA-276 0 None None None Never

Description Aleksandar Kostadinov 2008-01-04 18:55:22 UTC 
Date of First Response: 2008-01-09 06:18:38
project_key: SOA

Setting more permgen space for production config is a good idea IMO. I haven't done much investigation but seems like components of SOA-P require generally more of it. 

Particularly I can't run the whole JBoss WS test suite without increasing permgen (currently to max 256M). And let me repeat, this is not too much meaningful but lets me think that we do need more.
Comment 1 trev 2008-01-09 11:18:38 UTC 
See SOA-74, increasing default permgen is just a stopgap, setting it to any level will fail ultimately
Comment 2 trev 2008-01-10 18:08:30 UTC 
upped to 512m in run.bat, run.conf and server/production/run.conf
Comment 3 Aleksandar Kostadinov 2008-01-23 08:57:49 UTC 
I think that should be a good default.
Note You need to log in before you can comment on or make changes to this bug.