I think there was some stuff about this before, but what is the Slow Alarm
warning in the logs? I see a lot of this after my resin instance has been
running on my MacBook Pro (Lion) for a day or more. I often close the lid to
sleep it while I transport it.
I get entries like this:
[12-04-24
When I'm making changes to the code of a webapp, Resin kindly reloads it for
me. I can usually get a handful of reloads in before Resin complains about
being out of PermGen space.
Is there something I'm doing wrong in my app that it leaks like this?
--
Rick
On 24.04.2012 22:54, Rick Mann wrote:
When I'm making changes to the code of a webapp, Resin kindly reloads it for
me. I can usually get a handful of reloads in before Resin complains about
being out of PermGen space.
Is there something I'm doing wrong in my app that it leaks like this?
On Apr 24, 2012, at 14:32 , Olaf Krische wrote:
On 24.04.2012 22:54, Rick Mann wrote:
When I'm making changes to the code of a webapp, Resin kindly reloads it for
me. I can usually get a handful of reloads in before Resin complains about
being out of PermGen space.
Is there something
Well, yes and no. As I understand the problem, it really got bad around
the Java 5 timeframe because of the addition of Enumerations to the
language. What Resin does (and all auto-reloading Java containers do) is
to create a ClassLoader that contains all the code for your application.
When it
Out of PermGen space is almost always caused by a classloader leak which
occurs when a webapp is reloaded. It could be caused by either your own
code, third-party code, or in some case Java core classes.
You need to take heap dumps before and after webapp reload and use a heap
analyzer to see
Howard Leadmon schrieb am 23.04.2012 um 19:27 (-0400):
At that point it put up a nice red stop symbol,
and gave the following error:
Your session data was lost! Check your php.ini and make sure
session.save_path is set to an appropriate directory.
Check the php-ini config section here:
Hello Chris,
this actually makes me wonder: are enums eating so much space,
especially when compared to those things, that you release with the
classloader?
Heard about this for the first time. Interesting.
On 24.04.2012 23:41, Chris Pratt wrote:
that, since Enumerations are guaranteed to
On 04/24/2012 03:13 PM, Bill Au wrote:
Out of PermGen space is almost always caused by a classloader leak
which occurs when a webapp is reloaded. It could be caused by either
your own code, third-party code, or in some case Java core classes.
You need to take heap dumps before and after
Hi Rick.
After having had these issues for years, I started blogging about it and
how to find classloader leaks [1]. I also compiled a list of API calls
and third party libraries known to trigger these leaks [2], and as you
can see, it is quite common both to cause these problems yourself and
10 matches
Mail list logo
