| Exception Description: Operation not supported: [instantiateForUnitOfWorkValueHolder] [message #718757] |
Thu, 25 August 2011 05:14  |
sebastian.schneider
Messages: 9
Registered: January 2010 |
Junior Member |
|
|
Hello,
when upgrading from Eclipselink 2.1.3 to 2.3.0 I get the following stacktrace:
Caused by: org.eclipse.persistence.exceptions.ValidationException:
Exception Description: Operation not supported: [instantiateForUnitOfWorkValueHolder].
at org.eclipse.persistence.exceptions.ValidationException.operationNotSupported(ValidationException.java:1451) ~[org.eclipse.persistence.core-2.3.0.jar:2.3.0.v20110604-r9504]
at org.eclipse.persistence.internal.indirection.ProtectedValueHolder.instantiateForUnitOfWorkValueHolder(ProtectedValueHolder.java:52) ~[org.eclipse.persistence.core-2.3.0.jar:2.3.0.v20110604-r9504]
at org.eclipse.persistence.internal.indirection.UnitOfWorkValueHolder.instantiateImpl(UnitOfWorkValueHolder.java:156) ~[org.eclipse.persistence.core-2.3.0.jar:2.3.0.v20110604-r9504]
at org.eclipse.persistence.internal.indirection.UnitOfWorkValueHolder.instantiate(UnitOfWorkValueHolder.java:222) ~[org.eclipse.persistence.core-2.3.0.jar:2.3.0.v20110604-r9504]
at org.eclipse.persistence.internal.indirection.DatabaseValueHolder.getValue(DatabaseValueHolder.java:88) ~[org.eclipse.persistence.core-2.3.0.jar:2.3.0.v20110604-r9504]
at de.wirthedv.ticket.domain.Ticket._persistence_get_team(Ticket.java) ~[Ticket.class:na]
at de.wirthedv.ticket.domain.Ticket.getTeam(Ticket.java:223) ~[Ticket.class:na]
when accessing team on an Ticket Object. (Classes are weaved static)
@ManyToOne(fetch = FetchType.LAZY)
@JoinColumn(name = "TEAM_ID")
private Team team;
Is there anything I had to change in the config? While using Eclipselink 2.1.3 there is no error in the webapplication.
Thank you
Sebastian
[Updated on: Thu, 25 August 2011 11:52] Report message to a moderator |
|
|
|
|
| Re: (no subject) [message #719840 is a reply to message #719273] |
Mon, 29 August 2011 03:51  |
sebastian.schneider
Messages: 9
Registered: January 2010 |
Junior Member |
|
|
Okay thanks for this info.
After weaving the classes with 2.3.0 we get sometimes Nullpointerexceptions on @ManyToOne like showed in the first post but these fields are non-nullable in the database, so there can't be a null value. This happens with FetchType.LAZY and EAGER
Is there something we have to change also?
[Updated on: Tue, 30 August 2011 03:15] Report message to a moderator |
|
|
|
|
| Re: (no subject) [message #720548 is a reply to message #720537] |
Tue, 30 August 2011 15:41 |
sebastian.schneider
Messages: 9
Registered: January 2010 |
Junior Member |
|
|
Sorry there is no stacktrace beacause there is no exception rather than the NullPointerException when we try to acess the object, the problem that occurs is that the non-null values are null, e.g. team like shown before.
=> After restarting the tomcat other non-null columns are null values in the objects.
|
|
|
| Re: (no subject) [message #722737 is a reply to message #720548] |
Tue, 06 September 2011 11:34 |
 James Sutherland
Messages: 1844
Registered: July 2009 |
Senior Member |
|
|
Can you isolate the exact scenario that causes the issue? Perhaps log a bug if you can.
Are you putting objects will null values into your cache? If you disable the shared cache does the issue go away?
Are you mixing caching in some objects with no caching in others?
Do all classes/relationships have this issue, or specific ones? (like ones to objects that are not cached?)
Are you using fetch groups, or lazy basics?
If you refresh the object, does it resolve the issue?
Try the latest build to see if the issues still occur.
James : Wiki : Book : Blog
|
|
|
|
Powered by
FUDForum. Page generated in 0.02305 seconds
] 
Search
Help
Register
Login
Home
