Hi, Marcus
> OS: Win XP Pro SP3
>
> JVM: Installed is JRE 1.5.0_15, JRE 1.6.0_02, JRE 1.6.0_05, , JRE 6, JRE 1.6.0_10, JRE 1.4.2_12. How to check what JVM is really used by GlassFish?
>
You can check the $GF_HOMEconfig/asenv.conf for the AS_JAVA variable value.
> GlassFish: Java EE SDK 5 (9.1_01 build b09d-fcs)
>
> Artefact: EAR containing EJB-JAR, ApplicationClient-JAR, several libraries in /lib.
>
> Deploy is not incremental but always full, since I always do undeploy before I do deploy.
>
Can you use jmap to collect the heap information? jmap -heap <pid>
One other thing that might help is to see which instances are eating up
so much of the heap space.
You can get this info by using
jmap -histo <pid>
or
jmap -histo:live <pid>
where the latter command prints only those instances that are not
candidates for garbage collection.
Thanks,
- Hong
> Regards
> Markus
>
> -----Original Message-----
> From: Alexis.Moussine-Pouchkine_at_sun.com [mailto:Alexis.Moussine-Pouchkine_at_sun.com] On Behalf Of Alexis Moussine-Pouchkine
> Sent: Donnerstag, 5. Juni 2008 12:31
> To: users_at_glassfish.dev.java.net
> Subject: Re: Caused by: java.lang.OutOfMemoryError: PermGen space
>
> Which OS/JVM/GlassFish versions?
> What kind of artifact are you deploying? WAR, EAR?
> If this is indeed an issue with incremental deploys, it shouldn't
> affect production use.
> Earlier 9.0 (GFv1) bugs have been fixed in 9.1/2.0. See:
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=1855
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=2375
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=2315
>
> -Alexis
>
> On Jun 5, 2008, at 11:27, Markus Karg wrote:
>
>
>> So it seems it is not my fault at least. ;-)
>>
>> I have opened a bug report. Please add as much as you know about the
>> bug here:
>>
>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=5104
>>
>> Thanks
>> Markus
>>
>> From: Florent Blondeau [mailto:fblondeau_at_pingwy.com]
>> Sent: Donnerstag, 5. Juni 2008 10:59
>> To: users_at_glassfish.dev.java.net
>> Subject: Re: Caused by: java.lang.OutOfMemoryError: PermGen space
>>
>> Hi Marcus,
>>
>> Unfortunately, the only way to correct that is to restart the
>> server...
>> This is a known inconvenience. Many deployments without restarting
>> cause PermGen Space Error ("many" depends on
>> the maxPermSize parameter, among other things).
>> With my last conf, I wasn't able to deploy more than 6 or 7 times
>> without restarting. Now, we deploy 15-20 times before
>> getting this error.
>> A thread of this list talks about this issue, but I can't find it :-)
>>
>> Hope that helps
>>
>> Florent
>>
>> Pingwy
>> 27, rue des arènes
>> 49100 Angers
>>
>>
>> Markus Karg a écrit :
>> GlassFish told me this error message in the server.log.
>>
>> How to fix that?
>>
>> Thanks
>> Markus
>>
>> QUIPSY QUALITY GmbH & Co. KG
>> Ein Unternehmen der MES-Gruppe
>> Stuttgarter Strasse 23
>> D-75179 Pforzheim
>> Tel: 07231-9189-52
>> Fax: 07231-9189-59
>> www.quipsy.de
>> karg_at_quipsy.de
>> Registergericht Mannheim HRA 701214
>> Geschäftsführer: Nils Schroeder
>>
>> Diese E-Mail enthält persönliche, vertrauliche und vor Weitergabe
>> geschützte Informationen und ist ausschließlich für den vorgesehenen
>> o.g. Empfänger (Adressaten) bestimmt. Falls Sie diese E-Mail
>> versehentlich erhalten haben und nicht der vorgesehene Empfänger
>> sind, bitten wir Sie, die E-Mail und deren Anhänge nicht
>> aufzubewahren, nicht zu vervielfältigen, nicht zu nutzen und nicht
>> weiterzugeben. Bitte informieren Sie uns als Absender über diesen
>> Zustellungsfehler und löschen Sie die E-Mail.
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>