Memory Leak with Tomcat version update 3.2 to 6.0

Hi, I've been trying to update tomcat from 3.2 to 6.0. My issue is that I have a memory leak(s?) that make the web application unusable. Currently in my setup I am using these components:

Tomcat 6.0, sun JDK 1.6.0_01, mssql 2005, Microsoft SQL Server 2005 JDBC Driver 1.2, xalan 2.7.0, log4j 1.0.4 (should be only out of date component)

It is a fairly large application that uses xslt with xalan and java servlets to display web pages. There was no issue with memory leaks before the update from tomcat 3.2, sun jdk 1.4.2 and old xalan and jdbc (for mssql 2000) components.

My question for the community is, where should I be looking for my memory leak. Are there known issues with my setup?

thanks for your help,

Matt

[757 byte] By [mattcrwia] at [2007-11-27 9:33:43]
# 1

Just in case someone goes down the same road as me, my problem was actually the one listed on the page below. My threads are not being released after a StandardContext reload. Which I'm not sure if this leak applies to tomcat version <4 or not.

http://opensource.atlassian.com/confluence/spring/pages/viewpage.action?pageId=2669

mattcrwia at 2007-7-12 22:55:54 > top of Java-index,Enterprise & Remote Computing,Web Tier APIs...