Skip to:

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

Exception: An entity got loaded even though it was not part of the EntityInfo list

Description

while testing our project on Centos7 some integration tests failed with an exception:

org.hibernate.search.exception.AssertionFailure: An entity got loaded even though it was not part of the EntityInfo list at org.hibernate.search.query.hibernate.impl.CriteriaObjectInitializer.initializeObjects(CriteriaObjectInitializer.java:95) at org.hibernate.search.query.hibernate.impl.QueryLoader.executeLoad(QueryLoader.java:88) at org.hibernate.search.query.hibernate.impl.AbstractLoader.load(AbstractLoader.java:58) at org.hibernate.search.query.hibernate.impl.FullTextQueryImpl.list(FullTextQueryImpl.java:201) at org.hibernate.search.jpa.impl.FullTextQueryImpl.getResultList(FullTextQueryImpl.java:153)

no changes were done in the code. still running on Centos6 but fail on slave of Centos7

Activity

Yoann RodièreSeptember 26, 2023 at 9:37 AM

Hello,

This issue was reported against Hibernate Search 5.x or earlier, and doesn't seem to be relevant to newer Hibernate Search versions (6.x+).

In order to focus on newer versions, we are going to close this issue.

If you are still affected by this issue on Hibernate Search 6.0 or later, and have a reproducer, please comment here or reach out to us so we can reopen the issue.

If you are still affected by this issue on Hibernate Search 5.x, and want to provide a fix, please comment here or reach out to us so we can work out the next steps with you.

Cheers,
Yoann

Yoann RodièreMay 28, 2018 at 7:11 AM

Hi ,

I see you are using Hibernate Search version 5.5, which is no longer actively maintained: it's 3 years old and we have released 5 new minor versions since its was first published (5.6, 5.7, 5.8, 5.9 and 5.10). This version is likely to contain bugs that have been resolved in a later version.

We can have a look and try to fix the issue, especially because it may also affect newer versions, but the fix will likely be merged into a more recent version only (5.6 is currently the oldest maintained series).

It would help if you could:

  1. Check that the problem is still present with the latest 5.5 (5.5.8.Final) and the latest version of Hibernate ORM you can use in Search 5.5 (ORM version 5.1.14.Final)

  2. If possible, upgrade to at least Hibernate Search 5.6.4.Final (5.10.0.Final would be better, but that's a lot more work since you'll need to upgrade ORM to 5.3, too) and check that the problem is still present.

  3. Try to reproduce the problem in a separate, simple test case. We have https://github.com/hibernate/hibernate-test-case-templates/tree/master/search/hibernate-search-lucene. If you need a template for version 5.5, you will have to go back in time to commit 0c7f43be477d9403973061f06e2e306dcacb32bd: https://github.com/hibernate/hibernate-test-case-templates/tree/0c7f43be477d9403973061f06e2e306dcacb32bd/search/hibernate-search-lucene

Thanks in advance,
Yoann

Naama WeisfishMay 28, 2018 at 4:35 AM

not exactly. in the previous we use:
openjdk version "1.8.0_151"
OpenJDK Runtime Environment (build 1.8.0_151-b12)
OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)

Sanne GrinoveroMay 27, 2018 at 12:18 PM

But is it the same openjdk build on both Centos versions ?

Naama WeisfishMay 27, 2018 at 11:13 AM
Edited

openjdk version "1.8.0_161"
OpenJDK Runtime Environment (build 1.8.0_161-b14)
OpenJDK 64-Bit Server VM (build 25.161-b14, mixed mode)

what else can help?
again, we didn't change anything else (like database, dependencies version etc.)
only the centos.

Out of Date

Details

Assignee

Reporter

Fix versions

Affects versions

Priority

Created May 27, 2018 at 10:30 AM
Updated September 26, 2023 at 9:37 AM
Resolved September 26, 2023 at 9:37 AM

Flag notifications