Hi all,
Ok, seems this issue is resolved with the raised MaxPermSize.
Thanx so much for helping out - Guillaume and Michael especially!
I've read that the OutOufMemoryError - PermGen Space also might come from memory leaks in the actual code. But the most
commoncause seems to be (as already suggested in this thread) deployment without restarting the server.
In our case, I think (and hope=)) the Error occurs because of the large amount of classes used (like Guillaume
suggested).
Someone asked me to supply the Java- and JBoss versions we use, so:
Java version: 1.5.0_06
JBoss version: 4.2.2.GA
Thanx again, guys!
Håkan Jacobsson - System Developer
----------------------------------------------------------------
RELEVANT TRAFFIC EUROPE AB, Riddarg 17D, SE-114 57 Sthlm, Sweden
Mobile (+46) 736 56 97 58
Direct (+46) 8 56 24 98 05
Phone to office (+46) 8 678 97 50 || Fax (+46) 8 661 19 22
-----Ursprungligt meddelande-----
Från: Guillaume Cottenceau [mailto:gc@mnc.ch]
Skickat: den 8 januari 2008 17:43
Till: Håkan Jacobsson
Kopia: Michael Goldner; pgsql-jdbc@postgresql.org
Ämne: Re: SV: [JDBC] JBoss-related question
Håkan Jacobsson <hakan.jacobsson 'at' relevanttraffic.com> writes:
> Hi all,
>
> I tried jmap on the Jboss process id and below is the result.
[...]
> MaxPermSize = 88080384 (84.0MB)
[...]
> PS Perm Generation
> capacity = 86114304 (82.125MB)
> used = 86077472 (82.08987426757812MB)
> free = 36832 (0.035125732421875MB)
> 99.9572289407344% used
>
> -------------------------------------------------
>
> I'm not 100% on how to interpret the result - but looking at the last entry 'PS Perm Generation': 99.9%
> used, it doesn't look all that good.
It's counted compared to the currently maximum capacity, not tp
the maximum allowed capacity. You're really at 97.7% use, which
surely does not look good. You should at least increase the
MaxPermSize to 128MB, and then you should monitor that figure to
see how it behaves on your server, to make sure you don't run out
of space.
> I did restart JBoss and then I tested some stuff, before
> running jmap. So, this hasn't got to do with re-deployment
> without restarting Jboss.
It may have to do with just having a large number of classes in
your application container, as it's the case for us. It's not bad
by itself, it just needs a little more memory.
--
Guillaume Cottenceau, MNC Mobile News Channel SA, an Alcatel-Lucent Company
Av. de la Gare 10, 1003 Lausanne, Switzerland - direct +41 21 317 50 36
