org.hibernate.HibernateException: Unable to instantiate default tuplizer [org.hibernate.tuple.entity.PojoEntityTuplizer]

-
This Exception during the maven build in an hibernate based project could come due to various reasons.
Primarily one should look into the complete stack trace. The further exception usually do give clue of the actual problem.

I my case, the stack trace revealed the below issue
Exception in thread "main" org.hibernate.HibernateException: Unable to instantiate default tuplizer [org.hibernate.tuple.entity.PojoEntityTuplizer]
at org.hibernate.tuple.entity.EntityTuplizerFactory.constructTuplizer(EntityTuplizerFactory.java:110)
at org.hibernate.tuple.entity.EntityTuplizerFactory.constructDefaultTuplizer(EntityTuplizerFactory.java:135)
at org.hibernate.tuple.entity.EntityEntityModeToTuplizerMapping.(EntityEntityModeToTuplizerMapping.java:80)
at org.hibernate.tuple.entity.EntityMetamodel.(EntityMetamodel.java:323)
at org.hibernate.persister.entity.AbstractEntityPersister.(AbstractEntityPersister.java:456)
at org.hibernate.persister.entity.SingleTableEntityPersister.(SingleTableEntityPersister.java:131)
at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:84)
at org.hibernate.impl.SessionFactoryImpl.(SessionFactoryImpl.java:267)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1341)
at sample.PopulateMessages.main(PopulateMessages.java:13)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.hibernate.tuple.entity.EntityTuplizerFactory.constructTuplizer(EntityTuplizerFactory.java:107)
... 9 more
Caused by: java.lang.NoClassDefFoundError: javassist/util/proxy/MethodFilter
at org.hibernate.bytecode.javassist.BytecodeProviderImpl.getProxyFactoryFactory(BytecodeProviderImpl.java:49)
at org.hibernate.tuple.entity.PojoEntityTuplizer.buildProxyFactoryInternal(PojoEntityTuplizer.java:208)
at org.hibernate.tuple.entity.PojoEntityTuplizer.buildProxyFactory(PojoEntityTuplizer.java:186)
at org.hibernate.tuple.entity.AbstractEntityTuplizer.(AbstractEntityTuplizer.java:151)
at org.hibernate.tuple.entity.PojoEntityTuplizer.(PojoEntityTuplizer.java:78)
To resolve this, since i am using maven to build, I introduced the dependency on the javassist jar in the pom.xml file.

<dependency>
<groupId>javassist</groupId>
<artifactId>javassist</artifactId>
<version>3.4.GA</version>
</dependency>

This resolved the issue.


Comments

  1. AnonymousMarch 29, 2011 at 10:01 AM

    blablabla

    ReplyDelete
  2. Roshni BasuApril 12, 2011 at 8:26 AM

    I'm not using maven but tried adding javaassist.jar but still getting the same problem.Any other suggestion?

    ReplyDelete
  3. AbhisarMay 12, 2011 at 10:17 AM

    Can you provide more details? Let me know if the problem is still not resolved.

    ReplyDelete
  4. AnonymousJuly 5, 2011 at 6:45 AM

    I had the same problem and javaassist.jar did not help.

    In my case, this happened when getter and setter spellings are not consistent or when such setter/getter did not exist at all.

    For example:
    If you had a member with the name ABC
    and the getter was getMyABC()

    ReplyDelete
  5. AbhisarJuly 5, 2011 at 10:54 PM

    Thanks for adding your views

    ReplyDelete
    Replies
    1. AshuMarch 16, 2012 at 5:49 AM

      add the latest version of asm.jar
      Thanx,
      Ashutosh

      Delete
  6. AnonymousJanuary 19, 2012 at 10:16 AM

    In my case it did help. Although I don't understand this and neither do I get why this is not mentioned in the books you read about Spring/hibernate... Very strange and not at all trustworthy...

    ReplyDelete
  7. AshuMarch 16, 2012 at 5:51 AM

    add the latest version of asm.jar

    Ashutosh

    ReplyDelete
  8. AnonymousAugust 8, 2013 at 3:51 AM

    Hi Mr. Abhi.

    I'm getting error

    org.hibernate.HibernateException: Unable to instantiate default tuplizer [org.hibernate.tuple.entity.PojoEntityTuplizer]


    But here it throws an exception

    org.hibernate.MappingException: component class not found: com.pgapp.comm.InmateId

    Where I changed my class name InmateId as InmateData,

    then why it taking removed class

    Can u pls help me how to resove it..

    This Error caught in Myeclipse



    Thanks


    ReplyDelete
  9. gabaieagletonMarch 3, 2022 at 9:26 AM

    How to get to Mango Resort & Casino at Harrah's Philadelphia by Bus
    Directions to Mango Resort & Casino 남원 출장샵 (Harrah's 사천 출장샵 Philadelphia) with 부산광역 출장안마 public transportation. The following 태백 출장샵 transit lines have routes 영천 출장마사지 that pass near

    ReplyDelete

Post a Comment

Popular posts from this blog

Hibernate: a different object with the same identifier value was already associated with the session

-
People working with Hibernate might be familiar with the below error. org.springframework.orm.hibernate3.HibernateSystemException: a different object with the same identifier value was already associated with the session: nested exception is org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session This exception is generated when we try to load an instance object in session which has been already loaded by hibernate. Easier said than done. Hibernate considers two persistent entities identical if the two rows of the table can be said identical. Above error could be generated in many ways and there may be various solutions on net like using session merge etc to get away with the problem. I will discuss here the reason for me getting this problem and the way I resolved it. Below is the code which generated the exception for me. Following is the method which caused the exception @Transactional(propagation=Propagation.
Read more

BeanDefinitionStoreException: Failed to parse configuration class: Could not find class [javax.jms.ConnectionFactory]

-
If you are creating a Spring Boot application and see the following error stack . ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v2.2.0.RELEASE) 2020-06-27 19:30:32.786 INFO 35224 --- [ main] SchoolApplication : Starting SchoolApplication on LTUS76179 with PID 35224 (C:\personal\eclipse-workspace\apievolution\target\classes started by 381548 in C:\personal\eclipse-workspace\apievolution) 2020-06-27 19:30:32.796 INFO 35224 --- [ main] SchoolApplication : No active profile set, falling back to default profiles: default 2020-06-27 19:30:32.964 WARN 35224 --- [ main] ionWarningsApplicationContextInitializer : ** WARNING ** : Your ApplicationContext is unli
Read more