You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Paulo Alvim <al...@powerlogic.com.br> on 2005/04/07 22:48:29 UTC
JVM's perm size always increase after hot deploy to tomcat 5.0.28
Hi,
We had a "war" file with about 30MB using JSP pre-compilation and hot deploy
as suggested in the Tomcat web-site. But after using the hot deploy a few
times we received "out of memory" messages - in the JVM permanent area
(perm).
After migrating to 1.5.0_02 - to get better JVM information - we could see
that the used perm size always increase until this max size, in "every
Tomcat app reloading" (even with exploded files and Ant 'touches'). We
always lost 7 to 15MB of the perm area in every reload process - and this
area is never collected...
Anyone could help us with more information here (maybe about TC class
loaders or perm area)?
Is there anyone with the same problem?
Thanks in advance!
Paulo Alvim
Powerlogic
Brazil
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: RES: JVM's perm size always increase after hot deploy to tomcat 5.0.28
Posted by Rob Ross <ro...@earthlink.net>.
On Apr 7, 2005, at 3:34 PM, Paulo Alvim wrote:
> But is this really an official "known issue"? Do you know more links
> about
> the problem?
>
Well I just did a google search for "tomcat undeploy memory leak".
Here's three references:
http://66.102.7.104/search?q=cache:UhbMR4dZfhoJ:www.jroller.com/page/
sxh/20040105+tomcat+deploy+memory+leak&hl=en&client=safari
http://www.junlu.com/msg/153876.html
http://66.102.7.104/search?q=cache:GnJoip0vndkJ:mail-
archive.objectweb.org/barracuda/2004-06/
msg00028.html+tomcat+undeploy+memory+leak&hl=en&client=safari
Rob Ross, Senior Software Engineer
E! Networks
rross@eentertainment.com
---------------------------------------------------
"Beware of he who would deny you access to information, for in his
heart he dreams himself your master." -- Commissioner Pravin Lal
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
RES: JVM's perm size always increase after hot deploy to tomcat 5.0.28
Posted by Paulo Alvim <al...@powerlogic.com.br>.
But is this really an official "known issue"? Do you know more links about
the problem?
-----Mensagem original-----
De: Rob Ross [mailto:robross@earthlink.net]
Enviada em: quinta-feira, 7 de abril de 2005 17:53
Para: Tomcat Users List
Assunto: Re: JVM's perm size always increase after hot deploy to tomcat
5.0.28
Yes, this is a well known problem with redeploying wars in Tomcat. We
have to shutdown and restart the Tomcat server periodically after
redeploying a number of times.
It's a memory leak.
On Apr 7, 2005, at 1:48 PM, Paulo Alvim wrote:
> Hi,
>
> We had a "war" file with about 30MB using JSP pre-compilation and hot
> deploy
> as suggested in the Tomcat web-site. But after using the hot deploy a
> few
> times we received "out of memory" messages - in the JVM permanent area
> (perm).
>
> After migrating to 1.5.0_02 - to get better JVM information - we could
> see
> that the used perm size always increase until this max size, in "every
> Tomcat app reloading" (even with exploded files and Ant 'touches'). We
> always lost 7 to 15MB of the perm area in every reload process - and
> this
> area is never collected...
>
> Anyone could help us with more information here (maybe about TC class
> loaders or perm area)?
>
> Is there anyone with the same problem?
>
> Thanks in advance!
>
> Paulo Alvim
> Powerlogic
> Brazil
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
Rob Ross, Senior Software Engineer
E! Networks
rross@eentertainment.com
---------------------------------------------------
"Beware of he who would deny you access to information, for in his
heart he dreams himself your master." -- Commissioner Pravin Lal
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: JVM's perm size always increase after hot deploy to tomcat 5.0.28
Posted by Rob Ross <ro...@earthlink.net>.
Yes, this is a well known problem with redeploying wars in Tomcat. We
have to shutdown and restart the Tomcat server periodically after
redeploying a number of times.
It's a memory leak.
On Apr 7, 2005, at 1:48 PM, Paulo Alvim wrote:
> Hi,
>
> We had a "war" file with about 30MB using JSP pre-compilation and hot
> deploy
> as suggested in the Tomcat web-site. But after using the hot deploy a
> few
> times we received "out of memory" messages - in the JVM permanent area
> (perm).
>
> After migrating to 1.5.0_02 - to get better JVM information - we could
> see
> that the used perm size always increase until this max size, in "every
> Tomcat app reloading" (even with exploded files and Ant 'touches'). We
> always lost 7 to 15MB of the perm area in every reload process - and
> this
> area is never collected...
>
> Anyone could help us with more information here (maybe about TC class
> loaders or perm area)?
>
> Is there anyone with the same problem?
>
> Thanks in advance!
>
> Paulo Alvim
> Powerlogic
> Brazil
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
Rob Ross, Senior Software Engineer
E! Networks
rross@eentertainment.com
---------------------------------------------------
"Beware of he who would deny you access to information, for in his
heart he dreams himself your master." -- Commissioner Pravin Lal
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: JVM's perm size always increase after hot deploy to tomcat
5.0.28
Posted by Mieke Banderas <mi...@gamebox.net>.
edencane@gmail.com said:
>I'm afraid the subject of this post caused it to go to my spam box, :->
Was that before or after you moved that "s"?
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
RES: RES: JVM' sperm size always increase after hot deploy to tomcat 5.0.28
Posted by Paulo Alvim <al...@powerlogic.com.br>.
Hi!
Anyone could tell us if TC 5.5.x has improvements in the JVM's perm memory
area management?
-----Mensagem original-----
De: Paulo Alvim [mailto:alvim@powerlogic.com.br]
Enviada em: sábado, 9 de abril de 2005 14:53
Para: Tomcat Users List
Assunto: RES: RES: JVM' sperm size always increase after hot deploy to
tomcat 5.0.28
Thanks Michael...
But we had already tried to put both the "PropertyUtils.clearDescriptors();"
and the "Introspector.flushCaches();" in the ServletContextListener -
contextDestroyed and it didn't help so much (...) I'll try also with the
logging "LogManager.shutdown();".
But "try Tomcat 5.5x" - do you recommend that because it has improvements in
this area?
-----Mensagem original-----
De: Michael Echerer [mailto:mech@tngtech.com]
Enviada em: sábado, 9 de abril de 2005 07:23
Para: Tomcat Users List
Assunto: Re: RES: JVM' sperm size always increase after hot deploy to
tomcat 5.0.28
Paulo Alvim wrote:
> Thank you all
>
> It's good to know that we're not alone...but since we used to have
workable
> 'hot deploy' others pre-J2EE App Servers our customers will insist with
> that - maybe we'll have to reconsider other App Server as our main
> Open-Source production environment option.
>
> Does anyone know if JBoss 4 makes improvement in this area? I really can't
> believe that it's so hard...
>
Guess that won't help, because JBoss uses Tomcat as web container.
Check: http://issues.apache.org/bugzilla/show_bug.cgi?id=26135 and try
Tomcat 5.5x
Generally these undeploy memory leakage issues are mainly "coded" into
the webapp or in libraries. Some references won't be garbage collected
when undeploying. There seem to be problems with commons-logging and
beanutils, but could also be self-made, of course.
Cheers,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
RES: RES: JVM' sperm size always increase after hot deploy to tomcat 5.0.28
Posted by Paulo Alvim <al...@powerlogic.com.br>.
Thanks Michael...
But we had already tried to put both the "PropertyUtils.clearDescriptors();"
and the "Introspector.flushCaches();" in the ServletContextListener -
contextDestroyed and it didn't help so much (...) I'll try also with the
logging "LogManager.shutdown();".
But "try Tomcat 5.5x" - do you recommend that because it has improvements in
this area?
-----Mensagem original-----
De: Michael Echerer [mailto:mech@tngtech.com]
Enviada em: sábado, 9 de abril de 2005 07:23
Para: Tomcat Users List
Assunto: Re: RES: JVM' sperm size always increase after hot deploy to
tomcat 5.0.28
Paulo Alvim wrote:
> Thank you all
>
> It's good to know that we're not alone...but since we used to have
workable
> 'hot deploy' others pre-J2EE App Servers our customers will insist with
> that - maybe we'll have to reconsider other App Server as our main
> Open-Source production environment option.
>
> Does anyone know if JBoss 4 makes improvement in this area? I really can't
> believe that it's so hard...
>
Guess that won't help, because JBoss uses Tomcat as web container.
Check: http://issues.apache.org/bugzilla/show_bug.cgi?id=26135 and try
Tomcat 5.5x
Generally these undeploy memory leakage issues are mainly "coded" into
the webapp or in libraries. Some references won't be garbage collected
when undeploying. There seem to be problems with commons-logging and
beanutils, but could also be self-made, of course.
Cheers,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: RES: JVM' sperm size always increase after hot deploy to tomcat
5.0.28
Posted by Michael Echerer <me...@tngtech.com>.
Paulo Alvim wrote:
> Thank you all
>
> It's good to know that we're not alone...but since we used to have workable
> 'hot deploy' others pre-J2EE App Servers our customers will insist with
> that - maybe we'll have to reconsider other App Server as our main
> Open-Source production environment option.
>
> Does anyone know if JBoss 4 makes improvement in this area? I really can't
> believe that it's so hard...
>
Guess that won't help, because JBoss uses Tomcat as web container.
Check: http://issues.apache.org/bugzilla/show_bug.cgi?id=26135 and try
Tomcat 5.5x
Generally these undeploy memory leakage issues are mainly "coded" into
the webapp or in libraries. Some references won't be garbage collected
when undeploying. There seem to be problems with commons-logging and
beanutils, but could also be self-made, of course.
Cheers,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
RES: JVM' sperm size always increase after hot deploy to tomcat 5.0.28
Posted by Paulo Alvim <al...@powerlogic.com.br>.
Thank you all
It's good to know that we're not alone...but since we used to have workable
'hot deploy' others pre-J2EE App Servers our customers will insist with
that - maybe we'll have to reconsider other App Server as our main
Open-Source production environment option.
Does anyone know if JBoss 4 makes improvement in this area? I really can't
believe that it's so hard...
-----Mensagem original-----
De: edencane@gmail.com [mailto:edencane@gmail.com]
Enviada em: sexta-feira, 8 de abril de 2005 01:07
Para: Tomcat Users List
Assunto: Re: JVM' sperm size always increase after hot deploy to tomcat
5.0.28
Hi,
I'm afraid the subject of this post caused it to go to my spam box, :->
L.
On Apr 8, 2005 6:18 AM, Paulo Alvim <al...@powerlogic.com.br> wrote:
> Hi,
>
> We had a "war" file with about 30MB using JSP pre-compilation and hot
deploy
> as suggested in the Tomcat web-site. But after using the hot deploy a few
> times we received "out of memory" messages - in the JVM permanent area
> (perm).
>
> After migrating to 1.5.0_02 - to get better JVM information - we could see
> that the used perm size always increase until this max size, in "every
> Tomcat app reloading" (even with exploded files and Ant 'touches'). We
> always lost 7 to 15MB of the perm area in every reload process - and this
> area is never collected...
>
> Anyone could help us with more information here (maybe about TC class
> loaders or perm area)?
>
> Is there anyone with the same problem?
>
> Thanks in advance!
>
> Paulo Alvim
> Powerlogic
> Brazil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
--
............._
:| .| |.|/.|_
:|__.|_|.|\.|_
:0421 276 282.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: JVM' sperm size always increase after hot deploy to tomcat 5.0.28
Posted by ed...@gmail.com.
Hi,
I'm afraid the subject of this post caused it to go to my spam box, :->
L.
On Apr 8, 2005 6:18 AM, Paulo Alvim <al...@powerlogic.com.br> wrote:
> Hi,
>
> We had a "war" file with about 30MB using JSP pre-compilation and hot deploy
> as suggested in the Tomcat web-site. But after using the hot deploy a few
> times we received "out of memory" messages - in the JVM permanent area
> (perm).
>
> After migrating to 1.5.0_02 - to get better JVM information - we could see
> that the used perm size always increase until this max size, in "every
> Tomcat app reloading" (even with exploded files and Ant 'touches'). We
> always lost 7 to 15MB of the perm area in every reload process - and this
> area is never collected...
>
> Anyone could help us with more information here (maybe about TC class
> loaders or perm area)?
>
> Is there anyone with the same problem?
>
> Thanks in advance!
>
> Paulo Alvim
> Powerlogic
> Brazil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
--
............._
:| .| |.|/.|_
:|__.|_|.|\.|_
:0421 276 282.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org