You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Dmitri Blinov (Jira)" <ji...@apache.org> on 2020/04/06 11:29:00 UTC

[jira] [Commented] (JEXL-329) Uberspect may loose its Classloader

    [ https://issues.apache.org/jira/browse/JEXL-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076258#comment-17076258 ] 

Dmitri Blinov commented on JEXL-329:
------------------------------------

We supply JexlUberspect with our classloader to be able to create our classes in the future, so its possible for a classloader not to have any instances of the classes for the moment, so to be softly referenced, but that doesn’t mean we are ready to throw it away, right? 

> Uberspect may loose its Classloader
> -----------------------------------
>
>                 Key: JEXL-329
>                 URL: https://issues.apache.org/jira/browse/JEXL-329
>             Project: Commons JEXL
>          Issue Type: Bug
>    Affects Versions: 3.1
>            Reporter: Dmitri Blinov
>            Priority: Major
>
> In the current implementation Uberspect keeps references to its Introspector and ClassLoader via SoftReference. This means that when memory is short it can loose not only Introspector reference, which is OK, but also ClassLoader that was specified for resolving constructors, which looks like a bug.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)