Hi Ludo
On 11 May 2011 17:02, Ludovic Champenois <ludovic.champenois_at_oracle.com>wrote:
> On 5/11/11 7:44 AM, Manfred Riem wrote:
>
> Hi Matthias,
>
>
>
> While I understand where you are coming from I would seriously investigate
> which library is causing this problem. I routinely redeploy applications
> and
> I do not hit PermGen space errors for a long long long (months) while.
>
>
>
> I know that it is not a fix, but if you can isolate the culprit you might
> be
>
> able to replace it with a better library.
>
> Definitely...
> Also, file bugs on this library, ask the authors to run findbug on it,
> etc...A fix to such problem is possible and the fix would be in the library
> itself...
>
I agree it is the library causing the issue, but it's quite more complicated
than that.
Glassfish is quickly becoming the victim of Java's eco system of 10's of
thousands of libraries and better and better IDE's that hot deploy.
The classloader itself is involved with these MaxPerm gen issues. So it's
not as simple as, oops, I caused a memory leak in the library.
Have a look at :
http://java.net/jira/browse/GLASSFISH-13053 - Interesting
reading on the links
It should also be noted that I did 1000 deploys for most of the Java EE 6
samples before Glassfish 3 was released, and there were no issues. The issue
comes in when open source libaries are added to the project
What I am going to do is try to create 3+ samples that recreate this issue,
in an effort to solve this
regards
Richard