Your message dated Thu, 14 Sep 2006 14:44:13 +0200
with message-id <[EMAIL PROTECTED]>
and subject line memory leak in tc4
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: tomcat4
Version: 4.0.3-3woody3
Severity: normal
For a few years we where running our web application serving by
jserv-1.1.2 and IBMJava2-SDK-1.3 without any problems under significant
load. This application where written with servlet API 1.1 (jdk1.1). Now
when we migrate to jakarta tomcat we encountered memory leak with
tomcat-4.1.31 from debian. We tried Sun java VM j2sdk1.4.2_04 and
jdk1.5.0_01 with different garbage collection and memory heap
parameters: in all cases the end was the same. After few hours
application stopped with "java.lang.OutOfMemoryError". With IBM jdk1.4
it die after half of hour.
I solve this problem in two ways: downgrade tomcat to 4.0.3-3woody3 or
upgrade to 5.5.7. With both versions there are no memory leak or any
other problems. The 4.0.3 is too old but 5.5.7 is out of debian
distribution. That is why I need 4.1.31 from debian, but it has memory
leak with servlets. We have another application running under
tomcat-4.1.31 and there are no memory leak, but this is JSP application
without servlets.
If You need some details about application design, give Your questions.
We suppose this memory leak related to http sessions handling. You can
see this process comparing graphs for different version of tomcat:
http://fog.inist.ru/tomcat-4.1.31.jpg
http://fog.inist.ru/tomcat-4.0.3.jpg
http://fog.inist.ru/tomcat-5.5.7.jpg
There no any differences in the system settings, application configuration
or java VM: only in tomcat version.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: LANG=C, LC_CTYPE=ru_RU.koi8-r (charmap=KOI8-R)
Versions of packages tomcat4 depends on:
ii adduser 3.62 Add and remove users and groups
ii java-virtual-machine-dummy 0.3 Dummy Java virtual machine
ii libtomcat4-java 4.0.3-3woody3 Java Servlet engine -- core librar
ii logrotate 3.7-2 Log rotation utility
-- no debconf information
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
tomcat5 and tomcat5.5 are now available in debian and tomcat4 is removed.
According to the bts, the problem does not exist in tomcat5
Cheers,
- --
Arnaud <http://www.ressource-toi.org>
Java Trap: http://www.gnu.org/philosophy/java-trap.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFCU6c4vzFZu62tMIRArgWAJ9tupopTwZBaOtj5MgZ1WCnBf8KGACgjYG9
vLGwHqbZk7E/VR4R7ARdgIc=
=h75v
-----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
