tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 49414] Wrong memory leak detection: executor thread reported as web app thread
Date Fri, 25 Jun 2010 07:57:12 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=49414

Mark Thomas <markt@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Catalina                    |Catalina
            Version|trunk                       |6.0.26
            Product|Tomcat 7                    |Tomcat 6
   Target Milestone|---                         |default

--- Comment #3 from Mark Thomas <markt@apache.org> 2010-06-25 03:57:05 EDT ---
Tomcat does wait for requests to complete, I just got the default wait period
wrong by an order of magnitude. It waits 2 seconds, not 20 by default. The
unloadDelay attribute of the context controls this.

I have fixed this issue by examining the stack trace of threads with issues. I
decided to use the presence - or not - of the CoyoteAdator.service() call to
determine if this was a request thread. It is unlikely (but not impossible)
that even a customised Tomcat would have re-written that code.

This has been fixed in trunk and will be included in 7.0.1 onwards.

I have proposed the same fix for Tomcat 6.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message