hibernate-reactive: broken on Hibernate ORM master

Hibernate Reactive doesn’t work against current master of Hibernate ORM.

All the tests fail with something like:

Caused by: org.hibernate.AssertionFailure: possible non-threadsafe access to the session
	at org.hibernate.reactive.loader.ReactiveResultSetProcessor.initializeEntity(ReactiveResultSetProcessor.java:55)
	at org.hibernate.reactive.loader.ReactiveLoaderBasedResultSetProcessor.lambda$reactiveInitializeEntitiesAndCollections$3(ReactiveLoaderBasedResultSetProcessor.java:142)
	at org.hibernate.reactive.loader.ReactiveLoaderBasedResultSetProcessor$$Lambda$364/0000000000000000.apply(Unknown Source)
	at java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:995)

The cause appears to be the changes committed on Jul 30 by @yrodiere.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 16 (16 by maintainers)

Most upvoted comments

It’s available now https://in.relation.to//2020/08/10/hibernate-orm-5/

Sanne on Aug 10, 2020

I’m going to create one.

DavideD on Aug 4, 2020

So we’re going to need to come up with some way to find problems like this automatically, and it’s not clear what’s the best way to do that.

To begin with, we can create a JOB that tests with the latest ORM snapshot

I have something similar for Hibernate Search. Every time the ORM build finishes, I run a Hibernate Search build that uses the latest Hibernate ORM snapshot. However, I can only do that because I’m using Jenkins jobs, and they allow triggering a job after another job finishes.

yrodiere on Aug 4, 2020

To be specific, I believe it’s one of these commits that has caused the problem:

gavinking on Aug 3, 2020