openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Curtis (JIRA)" <>
Subject [jira] Reopened: (OPENJPA-1559) DataCacheManager initialization isn't thread safe.
Date Fri, 19 Mar 2010 19:48:27 GMT


Rick Curtis reopened OPENJPA-1559:

The change that I committed (rev. 921410) relies on double checked locking with a primitive
which I thought was safe to do.... but it appears that TestDataCacheScheduler.testMultithreadedInitialization
fails intermittently on a larger test machine. To date I've been unable to recreate this problem
on my dev machine. 

It appears that my fix still has a small window where this problem exists. Reopening to investigate
at a later date.

> DataCacheManager initialization isn't thread safe.
> --------------------------------------------------
>                 Key: OPENJPA-1559
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: datacache
>    Affects Versions: 2.0.0
>            Reporter: Rick Curtis
>            Assignee: Rick Curtis
>             Fix For: 2.0.0
> When running normally, some of OpenJPA configuration is lazily loaded and is not thread
safe. Normally this isn't an issue if one thread has a different configured object than another.
> Today I came across a problem when using the DataCache EvictionScheduler that multiple
scheduler threads can get created and kicked off. 

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

View raw message