Eclipse Community Forums: EclipseLink » NPE in CascadeLockingPolicy.initUnmappedFieldsQuery

Home » Eclipse Projects » EclipseLink » NPE in CascadeLockingPolicy.initUnmappedFieldsQuery

NPE in CascadeLockingPolicy.initUnmappedFieldsQuery [message #949858]

Fri, 19 October 2012 07:21

Eclipse User

Hi,

We are seeing strange behaviour in our application whereby the first time after the application starts and we try to persist a new JPA entity using entitymgr.persist() the following stacktrace occurs

Caused by: java.lang.NullPointerException: null
        at org.eclipse.persistence.internal.descriptors.CascadeLockingPolicy.initUnmappedFieldsQuery(CascadeLockingPolicy.java:242) ~[eclips
elink-2.3.3.jar:2.3.3.v20120629-r11760]
        at org.eclipse.persistence.internal.descriptors.CascadeLockingPolicy.initUnmappedFields(CascadeLockingPolicy.java:217) ~[eclipselink
-2.3.3.jar:2.3.3.v20120629-r11760]
        at org.eclipse.persistence.internal.descriptors.CascadeLockingPolicy.lockNotifyParent(CascadeLockingPolicy.java:273) ~[eclipselink-2
.3.3.jar:2.3.3.v20120629-r11760]
        at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.calculateChanges(UnitOfWorkImpl.java:651) ~[eclipselink-2.3.3.jar:2.3.3.
v20120629-r11760]
        at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1490) ~[eclipselink-2.
3.3.jar:2.3.3.v20120629-r11760]
        at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitRootUnitOfWork(RepeatableWriteUnitOfWork.java:267) ~[ec
lipselink-2.3.3.jar:2.3.3.v20120629-r11760]
        at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitAndResume(UnitOfWorkImpl.java:1143) ~[eclipselink-2.3.3.jar:2.3.3.
v20120629-r11760]
        at org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commitInternal(EntityTransactionImpl.java:84) ~[eclipselin
k-2.3.3.jar:2.3.3.v20120629-r11760]
        ... 53 common frames omitted

This is reproducible using eclipselink 2.3.3 and 2.4.0 and 2.4.1, did not try any other versions. Our application is deployed on WLS 10.3.4 and uses Spring 3.1 with the JpaTransactionManager. It is not related to a particular JPA entity, whatever the use case is we're executing - if it is the first time that a JPA entity needs to be saved we get the exception. After this first time everything works as normally.

If there is anything i can do to provide more debug info for this let me know, it's perfectly reproducible. The only thing i cannot provide easily is an isolated testcase.

Thanks !
Jorg

Re: NPE in CascadeLockingPolicy.initUnmappedFieldsQuery [message #956339 is a reply to message #949858]

Wed, 24 October 2012 08:32