[
https://issues.apache.org/jira/browse/OPENJPA-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-810.
-------------------------------------
Resolution: Fixed
Already fixed on master: MetaDataRepository gained repository locking
(_locking, on by default) and the opt-in Preload option
(MetaDataRepository.java:158-160) in 0efea474f/38a54f39f (OPENJPA-250,
2009-2010, first released in 2.0.0) to stop concurrent metadata-loading races.
No commit references OPENJPA-810 itself. Closing.
> ArgumentException thrown during query compilation in multithreaded application
> ------------------------------------------------------------------------------
>
> Key: OPENJPA-810
> URL: https://issues.apache.org/jira/browse/OPENJPA-810
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Jeremy Bauer
> Priority: Major
> Attachments: OPENJPA-810_trace.zip
>
>
> This problem was reported on the user mailing list by several users. It
> appeared to be an enhancement related problem similar to OPENJPA-234, but I
> was able to reproduce the problem (using a test app provided by Yann [1] via
> direct email) with classes that were enhanced with the PCEnhancer. Based on
> the trace, it appears that the metadata repository is being accessed
> concurrently by multiple threads and some persistent classes are not yet
> loaded while threads attempt to access them. The problem occurs more
> frequently when a) the persistent class list is large and b) trace is enabled.
> [1]
> http://n2.nabble.com/ArgumentException-%28Incomplete-initialisation-of-EntityManager%29-tc1577196.html#none
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
