[
http://jira.jboss.com/jira/browse/JBIDE-1175?page=all ]
Max Andersen updated JBIDE-1175:
--------------------------------
Component/s: JBossAS
Fix Version/s: 2.0.0.CR1
Affects Version/s: 2.0.0.Beta4
Assignee: Rob Stryker (was: Max Andersen)
but yes we could be nice and add some as default arguments; I suggest we don't put the
full amount in there just to not grab too much by default.
I suggest we this one
-Xms256m -Xmx512m -XX:MaxPermSize=256m
The user can always edit/remove them and i'm not sure --XX:PermSize will work/be
ignored on all vm's.
we've only previousl tested that -XX:MaxPermSize=256 gets hornored by sun vm and
ignored by IBM and JRockit (and fails on gcj, but that is not critical)
Ok by you gavin ?
Rob - can you make this happen ?
Make sure JBoss is launched with a big permgen
----------------------------------------------
Key: JBIDE-1175
URL:
http://jira.jboss.com/jira/browse/JBIDE-1175
Project: JBoss Tools
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 2.0.0.Beta4
Reporter: Gavin King
Assigned To: Rob Stryker
Priority: Critical
Fix For: 2.0.0.CR1
Where does JBoss AS get its permger size from when launched via Eclipse?
This issue may already have been addressed, but just in case it has not, make sure that
JBoss is run with the permgen settings recommended here:
http://docs.jboss.org/seam/1.2.1.GA/reference/en/html/gettingstarted.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira