Just an user hint:
Do you employ JMS on your project?
Did you check if there are object registered in JMX server after undeploys?
JMX looks like a good chance to memory leak. For an example of these
memory leaks see in Logback page a common error in projects using JMX
(
http://logback.qos.ch/manual/jmxConfig.html#leak).
BR,
---------------------------------------------------------------------------------------------------------------------
Gustavo Henrique Orair
Universidade Federal de Minas Gerais
------------------------------------------------------------------------------------------------------------------
2011/11/7 <hong.hz.zhang_at_oracle.com>:
> As you cannot share application, can you do a little more investigation from
> your side with your real production application to see what object(s) were
> leaking during redeployment?
>
> Thanks,
>
> - Hong
>
> On 11/6/2011 10:31 AM, Radim Kolar wrote:
>>
>> I tested memory leaks on redeploys with empty application made by grails
>> 2.0. Just run: grails create-app leakdemo;grails war
>> applications has extensive set of libraries included - springs, groovy,
>> hibernate... and while monitoring glassfish via jconsole it didnt discovered
>> any memory leaks on redeploys even after 20x redeploy.
>>
>> But using our real production application which is very similar to
>> included jars with exception sun SAAJ libs + springws added. it leaks memory
>> on redeploys. i have no war which i can share with public to reproduce that
>> problem.
>