[jira] Updated: (OPENEJB-1313) Memoizer may cause difficult to debug NullPointerException

["David Blevins (JIRA)" <ji...@apache.org>]

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

David Blevins updated OPENEJB-1313:
-----------------------------------

    Fix Version/s: 3.2-beta-1
         Assignee: karan singh malhi

> Memoizer may cause difficult to debug NullPointerException
> ----------------------------------------------------------
>
>                 Key: OPENEJB-1313
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1313
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 3.1.2
>         Environment: Applies to all environments as the Memoizer class is used by the logging system
>            Reporter: Mark Eschbach
>            Assignee: karan singh malhi
>             Fix For: 3.2-beta-1
>
>         Attachments: openejb-memoizer-npe.diff
>
>
> I found the constructor of the Memoizer class accepts null values in the constructor for the cache source algorithm while attempting to locate the source of an infinite loop in the logging system triggered while shutting down.  The acceptance of a null value will result in an NPE while attempting to file the cache at a later time, causing debugging difficulties.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.