Skip to:

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

Issues

Select view

Select search mode

 
11 of 11

BasicHibernateAnnotationsTest.testFilterOnCollection fails on jdk8

Fixed

Description

org.hibernate.test.annotations.entity.BasicHibernateAnnotationsTest
./gradlew hibernate-core:test -Dtest.single=entity/BasicHibernateAnnotationsTest --stacktrace
fails on jdk8, passes on jdk7

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created April 7, 2014 at 3:29 PM
Updated May 5, 2022 at 10:59 AM
Resolved May 5, 2022 at 10:59 AM

Activity

Martin SimkaMay 20, 2014 at 10:57 AM

and it fails also on oracle databases

Martin SimkaMay 20, 2014 at 10:56 AM

for the record, on jdk8 it fails with h2, postgresqlplus92, postresql92, mysql55 and it hangs with db2-97, db2-10, mssql2008r2, mssql2012, sybase157

Brett MeyerApril 7, 2014 at 6:19 PM

Just to re-iterate, it's a test-only fix for something BasicHibernateAnnotationsTest was doing incorrect to begin with, just simply exposed by jdk8.

Brett MeyerApril 7, 2014 at 5:20 PM
Edited

This stems from BasicHibernateAnnotationsTest's use of isCleanupTestDataRequired == true. When that's the case, the ORM test suite attempts a "delete from java.lang.Object", relying on polymorphism to delete all data from all entities. The order of those classes are determined by a simple Map#values in SessionFactoryImpl#getImplementors. It appears JDK8 has, once again, changed iteration ordering.

Really, I'm kind of surprised this worked to begin with. Realistically, deleting from java.lang.Object doesn't typically happen anywhere outside of tests. This will be a test-only fix, forcing #testFilterOnCollection to clean up its relationships prior to the one-shot delete (more correct to begin with).

Flag notifications