[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293?page=c...
]
Nicolas Daudin commented on HHH-1293:
-------------------------------------
Hi
I am having the same problem, but just with my JUnit tests.
I didn't change anything in particular in my mapping but i started getting the same
error this mornign while testing.
I used to have the problem, but it was on server-side and i solved it using the -server
flag.
But here obviously it can't work since i'm not using the server for my tests.
I'm running Hibernate 3.1.3, JUnit 3.8.1, Spring 1.2.9...
Thanks in advance ause it really bothers me...
java.lang.NoSuchMethodError: <persistent
class>.getHibernateLazyInitializer()
-----------------------------------------------------------------------------
Key: HHH-1293
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.1.1
Reporter: Andreas Schildbach
Assignee: Scott Marlow
Priority: Blocker
Fix For: 3.2.0.cr4
Attachments: CGLIBLazyInitializer.patch, CGLIBLazyInitializer.patch,
CGLIBLazyInitializer.patch3, CGLIBLazyInitializer.patch4, CGLIBProxyFactory.patch3,
hibernate.properties, hibernate3.jar, HibernateLazyInitializerTest.java, manysessions.tgz,
patch.CGLIBLazyInitializer.java, TestProcess.xml
As documented in
http://forum.hibernate.org/viewtopic.php?t=940119
some people (including me) are getting this exception with the final release of Hibernate
3.1:
java.lang.NoSuchMethodError:
de.schildbach.game.integration.HibernateGamePlayer.getHibernateLazyInitializer()Lorg/hibernate/proxy/LazyInitializer;
at
de.schildbach.game.integration.HibernateGamePlayer$$EnhancerByCGLIB$$afecb986.getHibernateLazyInitializer(<generated>)
at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:274)
at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:177)
at org.hibernate.type.TypeFactory.assemble(TypeFactory.java:398)
at org.hibernate.cache.entry.CacheEntry.assemble(CacheEntry.java:96)
at org.hibernate.cache.entry.CacheEntry.assemble(CacheEntry.java:82)
at
org.hibernate.event.def.DefaultLoadEventListener.assembleCacheEntry(DefaultLoadEventListener.java:520)
at
org.hibernate.event.def.DefaultLoadEventListener.loadFromSecondLevelCache(DefaultLoadEventListener.java:474)
at
org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:328)
at
org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:123)
at
org.hibernate.event.def.DefaultLoadEventListener.returnNarrowedProxy(DefaultLoadEventListener.java:202)
at
org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:169)
at
org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:87)
at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:869)
at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:838)
at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:266)
at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:177)
at
org.hibernate.collection.PersistentList.initializeFromCache(PersistentList.java:378)
at
org.hibernate.cache.entry.CollectionCacheEntry.assemble(CollectionCacheEntry.java:35)
at
org.hibernate.event.def.DefaultInitializeCollectionEventListener.initializeCollectionFromCache(DefaultInitializeCollectionEventListener.java:130)
at
org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:48)
at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1627)
at
org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344)
at
org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86)
at
org.hibernate.collection.AbstractPersistentCollection.readSize(AbstractPersistentCollection.java:109)
at org.hibernate.collection.PersistentList.size(PersistentList.java:91)
The exception varies with the actual persistent class in use. Most people seem to be
using JDK 1.5 and Linux. Some reports say that the exception does not happen from the very
start of the application, but it takes "several invocations"/"some
time" until it appear, but then it appears very often.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira