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/22 20:24:31 UTC
[Bug 60513] New: RMI leak cleaning is not thread safe
https://bz.apache.org/bugzilla/show_bug.cgi?id=60513
Bug ID: 60513
Summary: RMI leak cleaning is not thread safe
Product: Tomcat 8
Version: 8.0.30
Hardware: PC
OS: Mac OS X 10.1
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: markt@apache.org
Target Milestone: ----
As reported via users list.
https://lists.apache.org/thread.html/7b6c57b1838f180019bdd2bf8bf673b3b2365fe74f0e035b3b20cf8c@%3Cusers.tomcat.apache.org%3E
With multiple start/stop threads, concurrent calls are possible to the RMI leak
cleaning which is not thread safe.
--
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 60513] RMI leak cleaning is not thread safe
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60513
Remy Maucherat <re...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #1 from Remy Maucherat <re...@apache.org> ---
I added sync on the (static) objTable field from sun.rmi.transport.ObjectTable,
and this should fix the issue, although I didn't attempt to reproduce the
exception.
It will be in 9M16, 8.5.10, 8.0.40 and 7.0.74.
--
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