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

Posted to issues@commons.apache.org by "Henri Biestro (Jira)" <ji...@apache.org> on 2020/04/01 16:38:00 UTC

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

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

Henri Biestro resolved JEXL-329.
--------------------------------
    Resolution: Not A Problem

The soft reference may only be cleared if the class loader becomes softly referenced which implies that no instance of any class loaded through it is strongly referenced.
See ClassCreatorTest.testMany().

Beside the theory, I've (unfortunately) seen OOM occur -in production- but *never* seen JEXL loose its class loader. :-)

> 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)