You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2016/12/23 13:02:41 UTC

[Bug 60515] New: Improve ThreadLocal memory leak clean-up for ContainerBackgroundProcessor

https://bz.apache.org/bugzilla/show_bug.cgi?id=60515

            Bug ID: 60515
           Summary: Improve ThreadLocal memory leak clean-up for
                    ContainerBackgroundProcessor
           Product: Tomcat 8
           Version: 8.0.39
          Hardware: PC
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Catalina
          Assignee: dev@tomcat.apache.org
          Reporter: scholzb-hb@outlook.de
  Target Milestone: ----

Web applications using ThreadLocals inside HttpSessionListener implementations
may cause a class loader leak, since the listener calls are made in the
ContainerBackgroundProcessor thread, which is usually not renewed over time.

As already suggested in
https://bz.apache.org/bugzilla/show_bug.cgi?id=49159#c15, a separate thread
should be spawned for those callbacks into the webapp.

The current leak prevention (for Tomcat 7, 8 and 9) only considers the
application lifecycle callbacks, not the HttpSessionListener callbacks.

-- 
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

[Bug 60515] Improve ThreadLocal memory leak clean-up for ContainerBackgroundProcessor

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60515

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|NEW                         |RESOLVED

--- Comment #1 from Mark Thomas <ma...@apache.org> ---
This is already possible. If backgroundProcessorDelay is set to a positive
value for any Container (Engine, Host or Context), that container will be
provided with a separate background processing thread for it and its children.

By default a single thread from the Engine is used but per Context threads
would address this issue.

-- 
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

[Bug 60515] Improve ThreadLocal memory leak clean-up for ContainerBackgroundProcessor

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60515

Florian S. <fl...@gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |florian.scholz@gmx.de
                 OS|                            |All

-- 
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