Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Exception when mapping a class more than once

Description

When a class is mapped more than once, as defined in the documentation - http://docs.jboss.org/hibernate/orm/4.3/manual/en-US/html/ch05.html#mapping-entityname - a PersistenceException is thrown when creating the EntityManagerFactory.

stack trace:

javax.persistence.PersistenceException: Error build callback listeners; entity [org.example.ExampleEntity was already processed
at org.hibernate.jpa.event.internal.jpa.CallbackRegistryImpl.addEntityCallbacks(CallbackRegistryImpl.java:131)
at org.hibernate.jpa.event.internal.jpa.LegacyCallbackProcessor.processCallbacksForEntity(LegacyCallbackProcessor.java:71)
at org.hibernate.jpa.event.spi.JpaIntegrator.integrate(JpaIntegrator.java:150)
at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1857)
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850)
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843)
at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:399)
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842)
at org.hibernate.jpa.HibernatePersistenceProvider.createEntityManagerFactory(HibernatePersistenceProvider.java:73)
at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:54)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:55)

Attachments

2

Activity

Show:

Steve EbersoleNovember 5, 2015 at 2:29 AM

About to push a fix where I just skip the second attempt to register callbacks for a given class/callback combo - variation of option (2) above.

The improved solution can wait for the jandex-binding work, and is only really important for when we allow this case to additionally define different sets of callbacks per entity-name. Since that is not the case today, the quick fix works...

Steve EbersoleNovember 3, 2015 at 7:39 PM

There are 2 options I think to solve this.

  1. Have CallbackRegistryImpl track callbacks by entity name, not just the entity class.

  2. Have CallbackRegistryImpl skip putting entity class into its internal callback maps when a Class is found to have no callbacks.

(1) is the more correct solution, but requires some SPI changes. (2) works in the majority of cases like the reported ones.

So I'd suggest applying (2) to 5.0 and creating a enhancement request for 5.1 to change the signatures as needed to track callbacks by entity name.

Steve EbersoleOctober 28, 2015 at 11:08 AM

Thanks for verifying!

Wim DeblauweOctober 28, 2015 at 9:38 AM
Edited

I don't seem to have rights to update the issue, but I can verify that this still fails in 5.0. I have run the test from this PR on the master pointing to commit e6c1f511a30816963901fb4746163a849dd80226.

This is the output:

This issue prevents us from upgrading Hibernate beyond 4.2.17.

Steve EbersoleOctober 28, 2015 at 3:25 AM

As part of verifying that this issue affects 5.0, please just set the "Affects version". Leave the "verify-affects-5.0" label and leave the issue in "Awaiting Response" status; these are critical for us to be able to track these verifications and triage them. Thanks.

Fixed

Details

Assignee

Reporter

Labels

Time tracking

0.62h logged

Components

Fix versions

Affects versions

Priority

Created December 6, 2013 at 9:21 AM
Updated November 18, 2015 at 6:09 PM
Resolved November 5, 2015 at 2:32 AM