You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Dzmitry Kazimirchyk (JIRA)" <ji...@apache.org> on 2011/07/20 14:05:58 UTC
[jira] [Closed] (CAY-1583) context.getObjectStore() returning null
causing NullpointerException in DataMergeHandler
[ https://issues.apache.org/jira/browse/CAY-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dzmitry Kazimirchyk closed CAY-1583.
------------------------------------
Resolution: Fixed
Fix Version/s: 3.1M3
3.0.3
Assignee: Dzmitry Kazimirchyk
> context.getObjectStore() returning null causing NullpointerException in DataMergeHandler
> ----------------------------------------------------------------------------------------
>
> Key: CAY-1583
> URL: https://issues.apache.org/jira/browse/CAY-1583
> Project: Cayenne
> Issue Type: Bug
> Components: Core Library
> Affects Versions: 3.0.1
> Environment: sun Java 6 jre under both debian (squeeze) and ubuntu (maverik) linux with MySQL 5.1 using InnoDB.
> Reporter: Amaury SECHET
> Assignee: Dzmitry Kazimirchyk
> Fix For: 3.0.3, 3.1M3
>
>
> context.getObjectStore() return null, but nowhere in the code the constructor is called with null as objectStore
> This looks like a multithreading problem (object accessed before full initialization) or deserialization issue.
> However, I have a patch that's either, solve the issue, or at least make it almost impossible to trigger. Simply switch position of
> // use a setter to properly initialize EntityResolver
> setChannel(channel);
>
> form before the objectContext to after.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira