You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mark Thomas (JIRA)" <ji...@apache.org> on 2015/05/14 10:59:00 UTC

[jira] [Resolved] (POOL-289) Wrong ClassLoader used in BaseGenericObjectPool

     [ https://issues.apache.org/jira/browse/POOL-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Thomas resolved POOL-289.
------------------------------
    Resolution: Pending Closed

I've applied the patch as is. On balance I think the TCCL is more likely to be able to resolve the provided class name than the CL that loaded the current class so it makes sense to try that first.

> Wrong ClassLoader used in BaseGenericObjectPool
> -----------------------------------------------
>
>                 Key: POOL-289
>                 URL: https://issues.apache.org/jira/browse/POOL-289
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 2.3
>         Environment: All
>            Reporter: Luke Winkenbach
>            Priority: Critical
>             Fix For: 2.4
>
>         Attachments: classpath_fix.patch
>
>
> BaseGenericObjectPool uses Class.forName to load an EvictionPolicy with the thread context ClassLoader.  This does not work in OSGi environments.  If the class load fails with the thread context ClassLoader, the code should attempt to load using the BaseGenericObjectPool class's ClassLoader as well.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)