Re: Tomcat 5 Memory Leak
Which leak tracker tool are you using? Denis Barthélemy wrote: Hi, Our java based application is running on tomcat 5.0.3 on linux with JRE 1.4.2_08. Since the migration from tomcat 5.0.27 to 5.0.30, a bunch of our application's sessions are not correctly closed and so they stay in live using memory. In using a leak tracker tool, a memory leak has been found in org.apache.tomcat.util.threads.ThreadWithAttributes. I have found some information about this issue dealing with swallowOutput however the application doesn't use it and that doesn't correspond to our exact tomcat version. (http://mail-archives.apache.org/mod_mbox/tomcat-users/200502.mbox/%3CBAY16- [EMAIL PROTECTED]) Unfortunately at this time we don't have any more detail about it. Can somebody help? Denis B. Following the stack trace from leak tracker tool : com.one2team.one2web.common.Session2web org.apache.tomcat.util.threads.ThreadWithAttributes org.apache.tomcat.util.threads.ThreadPool$ControlRunnable org.apache.tomcat.util.threads.ThreadPool org.apache.jk.common.ChannelSocket java.util.Hashtable$Entry java.util.Hashtable org.apache.jk.core.WorkerEnv org.apache.jk.server.JkMain org.apache.jk.server.JkCoyoteHandler org.apache.coyote.tomcat5.CoyoteConnector org.apache.coyote.tomcat5.CoyoteRequest org.apache.coyote.Request org.apache.coyote.RequestInfo java.util.ArrayList org.apache.coyote.RequestGroupInfo org.apache.coyote.RequestInfo org.apache.commons.modeler.BaseModelMBean mx4j.server.MX4JMBeanMetaData java.util.HashMap$Entry java.util.HashMap mx4j.server.DefaultMBeanRepository mx4j.server.MX4JMBeanServer org.apache.catalina.core.StandardWrapper org.apache.tomcat.util.http.mapper.Mapper$Wrapper org.apache.tomcat.util.http.mapper.Mapper$Context org.apache.tomcat.util.http.mapper.Mapper java.lang.String - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- *:-.,_,.-:*'``'*:-.,_,.-:*:-.,_,.-:*'``'*:-.,_,.-: Rodrigo Assunção Engenheiro da Computação Accioly S/A Importação e Comércio E-mail: [EMAIL PROTECTED] Fone: (11)3352-8825 - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 5 Memory Leak
home made (the purpose is to explore the running time in inspecting private variables with JNI) -Message d'origine- De : Rodrigo Assunção [mailto:[EMAIL PROTECTED] Envoyé : vendredi 5 janvier 2007 11:41 À : Tomcat Users List Objet : Re: Tomcat 5 Memory Leak Which leak tracker tool are you using? Denis Barthélemy wrote: Hi, Our java based application is running on tomcat 5.0.3 on linux with JRE 1.4.2_08. Since the migration from tomcat 5.0.27 to 5.0.30, a bunch of our application's sessions are not correctly closed and so they stay in live using memory. In using a leak tracker tool, a memory leak has been found in org.apache.tomcat.util.threads.ThreadWithAttributes. I have found some information about this issue dealing with swallowOutput however the application doesn't use it and that doesn't correspond to our exact tomcat version. (http://mail-archives.apache.org/mod_mbox/tomcat-users/200502.mbox/%3CBAY16- [EMAIL PROTECTED])Unfortunately at this time we don't have any more detail about it. Can somebody help? Denis B. Following the stack trace from leak tracker tool : com.one2team.one2web.common.Session2web org.apache.tomcat.util.threads.ThreadWithAttributes org.apache.tomcat.util.threads.ThreadPool$ControlRunnable org.apache.tomcat.util.threads.ThreadPool org.apache.jk.common.ChannelSocket java.util.Hashtable$Entry java.util.Hashtable org.apache.jk.core.WorkerEnv org.apache.jk.server.JkMain org.apache.jk.server.JkCoyoteHandler org.apache.coyote.tomcat5.CoyoteConnector org.apache.coyote.tomcat5.CoyoteRequest org.apache.coyote.Request org.apache.coyote.RequestInfo java.util.ArrayList org.apache.coyote.RequestGroupInfo org.apache.coyote.RequestInfo org.apache.commons.modeler.BaseModelMBean mx4j.server.MX4JMBeanMetaData java.util.HashMap$Entry java.util.HashMap mx4j.server.DefaultMBeanRepository mx4j.server.MX4JMBeanServer org.apache.catalina.core.StandardWrapper org.apache.tomcat.util.http.mapper.Mapper$Wrapper org.apache.tomcat.util.http.mapper.Mapper$Context org.apache.tomcat.util.http.mapper.Mapper java.lang.String - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- *:-.,_,.-:*'``'*:-.,_,.-:*:-.,_,.-:*'``'*:-.,_,.-: Rodrigo Assunção Engenheiro da Computação Accioly S/A Importação e Comércio E-mail: [EMAIL PROTECTED] Fone: (11)3352-8825 - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 5 Memory Leak
Hi, Our java based application is running on tomcat 5.0.3 on linux with JRE 1.4.2_08. Since the migration from tomcat 5.0.27 to 5.0.30, a bunch of our application's sessions are not correctly closed and so they stay in live using memory. In using a leak tracker tool, a memory leak has been found in org.apache.tomcat.util.threads.ThreadWithAttributes. I have found some information about this issue dealing with swallowOutput however the application doesn't use it and that doesn't correspond to our exact tomcat version. (http://mail-archives.apache.org/mod_mbox/tomcat-users/200502.mbox/%3CBAY16- [EMAIL PROTECTED]) Unfortunately at this time we don't have any more detail about it. Can somebody help? Denis B. Following the stack trace from leak tracker tool : com.one2team.one2web.common.Session2web org.apache.tomcat.util.threads.ThreadWithAttributes org.apache.tomcat.util.threads.ThreadPool$ControlRunnable org.apache.tomcat.util.threads.ThreadPool org.apache.jk.common.ChannelSocket java.util.Hashtable$Entry java.util.Hashtable org.apache.jk.core.WorkerEnv org.apache.jk.server.JkMain org.apache.jk.server.JkCoyoteHandler org.apache.coyote.tomcat5.CoyoteConnector org.apache.coyote.tomcat5.CoyoteRequest org.apache.coyote.Request org.apache.coyote.RequestInfo java.util.ArrayList org.apache.coyote.RequestGroupInfo org.apache.coyote.RequestInfo org.apache.commons.modeler.BaseModelMBean mx4j.server.MX4JMBeanMetaData java.util.HashMap$Entry java.util.HashMap mx4j.server.DefaultMBeanRepository mx4j.server.MX4JMBeanServer org.apache.catalina.core.StandardWrapper org.apache.tomcat.util.http.mapper.Mapper$Wrapper org.apache.tomcat.util.http.mapper.Mapper$Context org.apache.tomcat.util.http.mapper.Mapper java.lang.String - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5 Memory Leak
On 1/4/07, Denis Barthélemy [EMAIL PROTECTED] wrote: Hi, Our java based application is running on tomcat 5.0.3 on linux with JRE 1.4.2_08. Since the migration from tomcat 5.0.27 to 5.0.30, a bunch of our application's sessions are not correctly closed and so they stay in live using memory. Why don't you try a stable version for alternation? 5.0.30 is a beta :-) Leon In using a leak tracker tool, a memory leak has been found in org.apache.tomcat.util.threads.ThreadWithAttributes. I have found some information about this issue dealing with swallowOutput however the application doesn't use it and that doesn't correspond to our exact tomcat version. (http://mail-archives.apache.org/mod_mbox/tomcat-users/200502.mbox/%3CBAY16- [EMAIL PROTECTED])Unfortunately at this time we don't have any more detail about it. Can somebody help? Denis B. Following the stack trace from leak tracker tool : com.one2team.one2web.common.Session2web org.apache.tomcat.util.threads.ThreadWithAttributes org.apache.tomcat.util.threads.ThreadPool$ControlRunnable org.apache.tomcat.util.threads.ThreadPool org.apache.jk.common.ChannelSocket java.util.Hashtable$Entry java.util.Hashtable org.apache.jk.core.WorkerEnv org.apache.jk.server.JkMain org.apache.jk.server.JkCoyoteHandler org.apache.coyote.tomcat5.CoyoteConnector org.apache.coyote.tomcat5.CoyoteRequest org.apache.coyote.Request org.apache.coyote.RequestInfo java.util.ArrayList org.apache.coyote.RequestGroupInfo org.apache.coyote.RequestInfo org.apache.commons.modeler.BaseModelMBean mx4j.server.MX4JMBeanMetaData java.util.HashMap$Entry java.util.HashMap mx4j.server.DefaultMBeanRepository mx4j.server.MX4JMBeanServer org.apache.catalina.core.StandardWrapper org.apache.tomcat.util.http.mapper.Mapper$Wrapper org.apache.tomcat.util.http.mapper.Mapper$Context org.apache.tomcat.util.http.mapper.Mapper java.lang.String - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
