DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28321>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28321 Tomcat JK2 Connector Memory Leak [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2004-04-13 17:48 ------- There are a couple of other entries in the changelog that are related, but yes, this should be fixed in 5.0.20+. You still should need to disable request-registration if you are using the JNI Channel, since the leak is still there. Fixing it here requires changes to the native side of the connector as well, since that is the only place that knows that a thread has died. Marking this as FIXED, since it looks like its a dup of the same-old request- registration problem. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
