You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Karl Pauls (Jira)" <ji...@apache.org> on 2020/10/08 09:13:00 UTC
[jira] [Resolved] (SLING-9802) Launcher Classloader is not
synchronizing loadClass correctly
[ https://issues.apache.org/jira/browse/SLING-9802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Pauls resolved SLING-9802.
-------------------------------
Resolution: Fixed
Fixed in https://github.com/apache/sling-org-apache-sling-feature-launcher/commit/f24d08bfd28c65908e113a3cf78a9a64c0d69d65
We now use the class loader lock and in turn, register the class loader to be parallel to not make that to heavy.
> Launcher Classloader is not synchronizing loadClass correctly
> -------------------------------------------------------------
>
> Key: SLING-9802
> URL: https://issues.apache.org/jira/browse/SLING-9802
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
> Affects Versions: Feature Model Launcher 1.1.6
> Reporter: Karl Pauls
> Assignee: Karl Pauls
> Priority: Major
> Fix For: Feature Model Launcher 1.1.8
>
>
> The default LauncherClassloader is not synchronizing its loadClass method correctly. As it just delegates to the findClass of the URLClassloader it extends, it needs to at a minimum lock on the classname it is trying to load - otherwise, it is possible that it will catch a LinkageError if the same class load is happening concurrently.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)