[infinispan-issues] [JBoss JIRA] (ISPN-9559) Server <modules> configuration with a single entry breaks classloading

[Adrian Nistor (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-9559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrian Nistor updated ISPN-9559:
--------------------------------
    Description: There's a bug in CacheContainerConfigurationBuilder introduced by changes for ISPN-7714. This happens only if we have a single module entry specified in the <modules> element of the cache container config or if we have a non-empty 'module' attribute.  The classloader of the specified module is used as the global classloader of the cache container. This is almost always wrong. We should instead have an AggregatedClassloader of the user specified classloader in module/modules + the infinispan subsystem classloader. If no module is specified then the infinispan subsystem classloader should be used.


> Server <modules> configuration with a single entry breaks classloading
> ----------------------------------------------------------------------
>
>                 Key: ISPN-9559
>                 URL: https://issues.jboss.org/browse/ISPN-9559
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core, Embedded Querying, Server
>    Affects Versions: 9.2.0.Final
>            Reporter: Adrian Nistor
>            Assignee: Adrian Nistor
>             Fix For: 9.4.0.Final
>
>
> There's a bug in CacheContainerConfigurationBuilder introduced by changes for ISPN-7714. This happens only if we have a single module entry specified in the <modules> element of the cache container config or if we have a non-empty 'module' attribute.  The classloader of the specified module is used as the global classloader of the cache container. This is almost always wrong. We should instead have an AggregatedClassloader of the user specified classloader in module/modules + the infinispan subsystem classloader. If no module is specified then the infinispan subsystem classloader should be used.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)