Sanne Grinovero

This was fixed now by #27802 - bear in mind that you might need to use `@ActivateRequestContext` going forward, as an incoming message listener won't have the scope by default:...

This looks like the same issue as others have reported: not using a transaction and/or not delegating to the right thread. IMO it's Panache Reactive which should not allow this...

(I don't know for sure and will let @DavideD reprodice and confirm, I'm just suspecting this might be the case since I see RestEasy being used in the stacktrace)

> You say that the problem is resteasy? even if concurrent panache reactive code work fine with just before execute a call to non-concurrent panache code? Well it's not RESTEasy's...

> I do not know how initialization connections works in panache reactive, but from the behavior and the error "Session/EntityManager is closed" all this looks like initialization connections trouble in...

@FroMage please see `org.hibernate.reactive.common.InternalStateAssertions` : it expects a system property to be set to enable the assertions that Davide is mentioning. I had hopes to enable these assertions by default,...

BTW the system property is set for the integration tests using Hibernate Reactive which don't use Panache; see: - integration-tests/hibernate-reactive-postgresql/pom.xml - integration-tests/hibernate-reactive-db2/pom.xml - integration-tests/hibernate-reactive-mysql/pom.xml

@FroMage right, I need you to patch Panache Reactive to run things on the right thread. Enabling the assertions should help you to verify being on the right track -...

@geoand sure that helps but there's a deeper issue if we don't guarantee all mutations-executing code is not run on the expected thread. So another key difference is that `withTransaction`...

Agreed. Sorry people, will have to be patient as the switch to Jakarta takes priority and some "projects" are better not run in parallel. In the meantime I would suggest...