Details
-
Enhancement
-
Resolution: Fixed
-
P4
-
None
-
b39
-
generic
-
generic
-
Not verified
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8084191 | emb-9 | Claes Redestad | P4 | Resolved | Fixed | team |
Description
Current code in j.l.ClassLoader and j.l.Package for retrieving packages use coarse-grained synchronization on shared collections and could be simplified by using concurrent utilities.
Furthermore, when defining Packages, the reading of Manifests from jar files is synchronized globally, which prohibits reading of manifests from different jar files in parallel, which could be a startup bottleneck for some applications.
Furthermore, when defining Packages, the reading of Manifests from jar files is synchronized globally, which prohibits reading of manifests from different jar files in parallel, which could be a startup bottleneck for some applications.
Attachments
Issue Links
- backported by
-
JDK-8084191 Simplify the synchronization of defining and getting java.lang.Package
- Resolved
- relates to
-
JDK-8061804 Re-examine Package of the same name allowed from ClassLoader.getPackages
- Closed
-
JDK-8055854 Examine overhead in java.net.URLClassLoader
- Closed