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 2017/01/21 08:45:28 UTC

[Bug 60620] New: [JRE] Memory leak found in java.util.concurrent.ForkJoinPool

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

            Bug ID: 60620
           Summary: [JRE] Memory leak found in
                    java.util.concurrent.ForkJoinPool
           Product: Tomcat 9
           Version: 9.0.0.M15
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
          Assignee: dev@tomcat.apache.org
          Reporter: knst.kolinko@gmail.com
  Target Milestone: -----

Filing a bug for an already fixed issue, to summarize discussions spawned
across different mailing lists, and for better changelog.


See "Tomcat 8, 8.5 and 9 returning another apps environment with
context.lookup() from a .parallelStream()", 2017-01-08 on users@
http://markmail.org/message/qcy6rqhw52sspyv7

See "Memory leak found in java.util.concurrent.ForkJoinPool", 2017-01-09 on
dev@
http://markmail.org/message/7w5wspqeayx7dr5x

-- 
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 60620] [JRE] Memory leak found in java.util.concurrent.ForkJoinPool

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

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

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

--- Comment #3 from Mark Thomas <ma...@apache.org> ---
Fixed in r1780268 for 8.0.42 onwards.

-- 
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 60620] [JRE] Memory leak found in java.util.concurrent.ForkJoinPool

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

Konstantin Kolinko <kn...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|                            |All

--- Comment #1 from Konstantin Kolinko <kn...@gmail.com> ---
A workaround for this Oracle JRE bug was added to memory leaks protection code
in Tomcat 7.0.74 (r1778068), 8.5.11 (r1778065), 9.0.0.M17 (r1778061)

The fix has not been applied to Tomcat 8.0 yet.

Note that compilation of SafeForkJoinWorkerThreadFactory requires Java 7 and
later. People who use two separate Eclipse projects for Tomcat 7 (separating
code that requires java 6 and java 7 into different projects) need to update
their include / exclude patterns.

The sample projects were updated in r1779707, to be in 7.0.76.

-- 
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 60620] [JRE] Memory leak found in java.util.concurrent.ForkJoinPool

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

Konstantin Kolinko <kn...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Catalina                    |Catalina
   Target Milestone|-----                       |----
            Product|Tomcat 9                    |Tomcat 8
            Version|9.0.0.M15                   |8.0.39

--- Comment #2 from Konstantin Kolinko <kn...@gmail.com> ---
Moving the issue to Tomcat 8.0, as the fix has not been applied there yet.

As a variant, we can add the helper class but keep the protection feature off
by default. This may wait a while, to get more feedback.

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