[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1293) java.lang.NoSuchMethodError: <persistent class>.getHibernateLazyInitializer()

[Darryl M. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293?page=comments#action_22126 ] 

Darryl Miles commented on HHH-1293:
-----------------------------------

Just to say my code has been working fine with tomcat started up in "-server" mode rather than "-client" the default that jsvc was picking up.

I was under the impression "-server" make the JVM optimize the code SOONER as in it always runs compiles into optimized form first then runs it, there is no interpreted code run, nor any mixed, therefore there is no hotspot working (hotspot I've understand to be an optimization technique which decides when to turn -Xint into machine code based on runtime statistics working out the most executed code, a trade off between startup time and execution time, I believe hotspot is used with -client that support mixedmode but not with -server, since everything is optimized before execution).

With JVM 1.5.0_06 I understand things to be:

-Xint forced interpreted mode only, disable hotspot and disable optimization
-client starts off with interpreted mode, and hotpost decides if/when a block of code is to migrate to optimized form
-server always takes bytecode and optimizes before execution


I guess the bug is really as Steve suggests, in the procedure the JVM uses to migrate with hotspot to fully a optimized unit of code and then migrate execution within the application from -Xint to the optimized code.  If the problem does not turn up with -Xint nor with -server then this code migration technique process has to be the problem.


> java.lang.NoSuchMethodError: <persistent class>.getHibernateLazyInitializer()
> -----------------------------------------------------------------------------
>
>          Key: HHH-1293
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1293
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.1.1
>     Reporter: Andreas Schildbach
>     Priority: Blocker

>
>
> 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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira