Closed GoogleCodeExporter closed 9 years ago
Are you doing this in an Amazon EC2 micro instance? I believe there is a post
about increasing the PERMGen space with a JVM parameter. Will take a look.
Original comment by gm2...@cerner.com
on 3 May 2011 at 9:17
You can increase the max PermGen size by editing the catalina.sh file. An
appropriate place may be after the following lines.
if [ -z "$LOGGING_MANAGER" ]; then
JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager"
else
JAVA_OPTS="$JAVA_OPTS $LOGGING_MANAGER"
fi
Add the following line (this sets the max PermGen size to 64 MB):
JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize 64m"
If you are still seeing the error, I would suggest raising it to 128m.
Original comment by gm2...@cerner.com
on 5 May 2011 at 11:59
My bad. Use this line:
JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=64m"
Original comment by gm2...@cerner.com
on 5 May 2011 at 12:02
Greg's suggestion will probably work. In the bare-metal documentation we have
the following recommendation:
-XX:PermSize=256M -XX:MaxPermSize=256M
Let us know if this fixes the problem.
Original comment by bgran...@harris.com
on 5 May 2011 at 1:20
Original comment by bgran...@harris.com
on 5 May 2011 at 1:22
Does there need to be a fix for this? I assume this is an application
server/JVM issue rather than Direct codebase.
Original comment by BrianCHo...@gmail.com
on 5 May 2011 at 7:06
Resolving this issue.. if the problem persists we will open it back up.
Original comment by bgran...@harris.com
on 9 May 2011 at 10:05
Original issue reported on code.google.com by
NFinst...@gmail.com
on 3 May 2011 at 7:54