Bug 777760 (SOA-276)

Summary:	permgen space too low
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Aleksandar Kostadinov <akostadinov>
Component:	Configuration	Assignee:	trev <tkirby>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2 Beta 1
Target Milestone:	---
Target Release:	4.2 Beta 2
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-276
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-01-23 08:57:49 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 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.