java/114644: tomcat goes out of PermSpace, jvm crashes

Tomas Verbaitis tomasv at megalogika.lt
Mon Feb 11 07:26:30 PST 2008


> Hi, does anyone know whether anyone is working/looking at this issue?
> Apparantly it has been open since July 17th, 2007.  I looked on
> http://lists.freebsd.org/pipermail/freebsd-java/2007-July/006476.html
> and 'State' is on 'open'.

Thanks for reminding about this issue. Problems with PermGen space are
quite common for all contemporary Java applications, just google around
for the "tomcat PermGen" and see... AFAIU the key is that by default
Java allocates too little memory for object that are kept around
permanently and not garbage collected.

There is a workaround for this issue: specifying more memory. With Java
1.5 and 1.6 the following switches work good (for Eclipse; although
my development Tomcat server, which has contexts reloaded often, crashes
when running out of PermGen space, production machines have Tomcat 5.0
and 5.5 running for months without this problem):

-XX:PermSize=128M -XX:MaxPermSize=512M

The first option specifies starting PermGen space size, the second --
how big can it grow. Exact values depend on your application's object
creation patterns.

You should put these options into rc.conf variable tomcat55_java_opts.

As Tomcat 5.5 port maintainer, I guess I could a pkg-mesg with the above
information, at least. Specifying some default tomcat55_java_opts values
seems a bit unreasonable, as -XX Java VM options may disappear without
notice.

-- 
Tomas "Verbaitis" Verbaitis ** http://megalogika.lt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-java/attachments/20080211/062618e2/attachment.pgp


More information about the freebsd-java mailing list