Meow,
If it's after several [un]deploy cycles that's certainly because a Classloader
(and the Class objects it loaded) cannot be recycled. They are stored in the
permanent heap generation by the jvm, and when you redeploy a new class loader
is created.
Sadly and from what I know/understand, every jee container is subject to this.
The only work around is to restart it.
And that could lead to the following : always restart when [un]deploying in
production.
:(
I'm I right ?
/Paul
Le Mercredi 07 Avril 2010 14:49:09, Richard Kolb a écrit :
> Hi Cats
>
> Is anyone else hitting this issue on a regular basis ?
> It really frustrates me as I seem to hit this almost every day while doing
> web development in NetBeans 6.8.
> And these are test projects, nothing big at all.
>
> I know there was some chatter about this issue a while back, but nobody
> could put their finger on the issue.
> It still seems to me, it happens on many many deploys.
>
> I would really hate this to happen in a production environment.
>
> regards
> Richard.