Hi Heiko, your situation seems related to this one (also see related jira issue http://issues.apache.org/jira/browse/OPENJPA-453): http://openjpa.208410.n2.nabble.com/NullPointerException-in-pcReplaceField-td2979657.html#a2979657
Although in this scenario the nullpointer relates to the statemanager of the embedded object. You do have an embedded primary key object, however the nullpointer seems to happen in the owning object? I can imagine that nullifying the statemanager happens with the refresh() call. My own experience is that it happens with the evict() or commit() with retainValues set to false. Personally I think this really is a problem related to multithreading in the internal structures of OpenJPA, since the nullpointer happens in code generated by OpenJPA. Accessing the statemanager and at the same time nullifying it is something OpenJPA code is aware of, not the application programmer. regards, Christiaan -- View this message in context: http://openjpa.208410.n2.nabble.com/NullPointerException-in-pcGet-Method-tp5337474p5345501.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
