You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (Jira)" <ji...@apache.org> on 2024/12/13 08:39:00 UTC
[jira] [Updated] (SLING-11022) Commons Classloaders should be parallel capable where possible
[ https://issues.apache.org/jira/browse/SLING-11022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert updated SLING-11022:
-----------------------------------
Fix Version/s: Commons FileSystem ClassLoader 1.0.18
(was: Commons FileSystem ClassLoader 1.0.16)
> Commons Classloaders should be parallel capable where possible
> --------------------------------------------------------------
>
> Key: SLING-11022
> URL: https://issues.apache.org/jira/browse/SLING-11022
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Affects Versions: Commons ClassLoader 1.4.4, File System ClassLoader 1.0.14
> Reporter: Karl Pauls
> Assignee: Karl Pauls
> Priority: Major
> Fix For: Commons ClassLoader 1.4.6, Commons FileSystem ClassLoader 1.0.18
>
>
> We are not registering our class loaders in commons class loader and commons file system class loader as parallel capable - as a consequence, we are synchronizing on the global lock per class loader which can cause unnecessary contention.
> We should register them as parallel capable and explicitly use the class loading lock where necessary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)