Quarkus 3.x - Mutiny, Fungy and Reactive Panache error with IllegalStateException: HR000068

[chengkuangan]

Hi,

I am upgrading from Quarkus 2.x to 3.x with purpose to use the @WithSession for Panache and I hit into the following error which can be seen from the bottom on this post.

Current Quarkus version: 3.0.2.Final

I wonder if Reactive Panache supported in Fungy in version 3.x? When I was testing in Quarkus version 2.16.5.Final, the the code seems to work but with some hiccups as reported in 23739 , and that's the reason I move to 3.x.

Should this be coding mistake at my end or should this be a bug?

The following is the code snippet, with the ProviderEntity extending io.quarkus.hibernate.reactive.panache.PanacheEntityBase

    @Funq("providers")
    @WithSession
    public Uni<List<ProviderEntity>> getProviders(){
        return ProviderEntity.listAll();
    }

Error with @WithSession annotation:

ERROR [io.qua.ver.htt.run.QuarkusErrorHandler] (executor-thread-2) HTTP Request to /providers failed, error id: 18aa9967-0c68-44bd-8fd8-3241d3202a9f-7: io.quarkus.funqy.runtime.ApplicationException: java.lang.IllegalStateException: HR000068: This method should exclusively be invoked from a Vert.x EventLoop thread; currently running on thread 'executor-thread-1'
        at io.quarkus.funqy.runtime.FunctionInvoker.lambda$invoke$0(FunctionInvoker.java:126)
        at io.smallrye.context.impl.wrappers.SlowContextualFunction.apply(SlowContextualFunction.java:21)
...
...
...
Caused by: java.lang.IllegalStateException: HR000068: This method should exclusively be invoked from a Vert.x EventLoop thread; currently running on thread 'executor-thread-1'

Error without @WithSession annotation:

io.quarkus.funqy.runtime.ApplicationException: java.lang.IllegalStateException: No current Mutiny.Session found
        - no reactive session was found in the context and the context was not marked to open a new session lazily
        - you might need to annotate the business method with @WithSession
        at io.quarkus.funqy.runtime.FunctionInvoker.invoke(FunctionInvoker.java:136)
        at io.quarkus.funqy.runtime.bindings.http.VertxRequestHandler.dispatch(VertxRequestHandler.java:141)
        at io.quarkus.funqy.runtime.bindings.http.VertxRequestHandler.lambda$handle$0(VertxRequestHandler.java:98)
        at io.quarkus.vertx.core.runtime.VertxCoreRecorder$14.runWith(VertxCoreRecorder.java:576)
        at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2513)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1538)
        at org.jboss.threads.DelegatingRunnable.run(DelegatingRunnable.java:29)
        at org.jboss.threads.ThreadLocalResettingRunnable.run(ThreadLocalResettingRunnable.java:29)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.lang.IllegalStateException: No current Mutiny.Session found
        - no reactive session was found in the context and the context was not marked to open a new session lazily
        - you might need to annotate the business method with @WithSession

[quarkus-bot[bot]]

/cc @FroMage (panache), @cescoffier (mutiny), @jponge (mutiny), @loicmathieu (panache), @matejvasek (funqy), @patriot1burke (funqy)

[mwieczorkiewicz]

@chengkuangan - Can notice the same issue on 3.2.2.Final. Very interestingly - even if you omit the Panache (and implement the repository with SessionFactory the problem still persists (as long as we're talking about Funqy, of course).

I was able to identify a workaround (not sure if it's correct - I am not necessarily a Java guy, so I am not sure if it's a good practice, but did the trick for me) - essentially if you implement a repository with a SessionFactory and then run the whole operation with .runSubscriptionOn(MutinyHelper.executor(vertx.getOrCreateContext())) - it should work.

Something like this:

@ApplicationScoped
public class MyEntityRepository {

    @Inject
    SessionFactory sessionFactory;

    @Inject
    Vertx vertx;

    public Uni<MyEntity> save(MyEntity me) {
        return sessionFactory.withTransaction((session, tx) -> session.persist(me))
                .replaceWith(me)
                .runSubscriptionOn(MutinyHelper.executor(vertx.getOrCreateContext()));
    }
}

What's more interesting is that when you try to enforce Panache to run on Vert.x Event Loop (via runSubscriptionOn) it's ends up having a StackOverflowError.

io.quarkus.funqy.runtime.ApplicationException: java.lang.StackOverflowError
	at io.quarkus.funqy.runtime.FunctionInvoker.lambda$invoke$0(FunctionInvoker.java:126)
	at io.smallrye.context.impl.wrappers.SlowContextualFunction.apply(SlowContextualFunction.java:21)
	at io.smallrye.mutiny.operators.uni.UniOnFailureTransform$UniOnFailureTransformProcessor.onFailure(UniOnFailureTransform.java:54)
	at io.smallrye.mutiny.operators.uni.UniOperatorProcessor.onFailure(UniOperatorProcessor.java:55)
	at io.smallrye.mutiny.operators.uni.UniOnItemOrFailureFlatMap$UniOnItemOrFailureFlatMapProcessor.onFailure(UniOnItemOrFailureFlatMap.java:67)
	at io.smallrye.mutiny.operators.uni.UniOnItemOrFailureFlatMap$UniOnItemOrFailureFlatMapProcessor.onFailure(UniOnItemOrFailureFlatMap.java:67)
	at io.smallrye.mutiny.operators.uni.builders.UniCreateFromKnownFailure$KnownFailureSubscription.forward(UniCreateFromKnownFailure.java:38)
	at io.smallrye.mutiny.operators.uni.builders.UniCreateFromKnownFailure.subscribe(UniCreateFromKnownFailure.java:23)
	at io.smallrye.mutiny.operators.AbstractUni.subscribe(AbstractUni.java:36)
	at io.smallrye.mutiny.operators.uni.UniOnItemOrFailureFlatMap$UniOnItemOrFailureFlatMapProcessor.performInnerSubscription(UniOnItemOrFailureFlatMap.java:99)
	at io.smallrye.mutiny.operators.uni.UniOnItemOrFailureFlatMap$UniOnItemOrFailureFlatMapProcessor.onItem(UniOnItemOrFailureFlatMap.java:54)
	at io.smallrye.mutiny.operators.uni.UniOnTermination$UniOnTerminationProcessor.onItem(UniOnTermination.java:39)
	at io.smallrye.mutiny.operators.uni.UniOperatorProcessor.onItem(UniOperatorProcessor.java:47)
	at io.smallrye.mutiny.operators.uni.builders.UniCreateFromCompletionStage$CompletionStageUniSubscription.forwardResult(UniCreateFromCompletionStage.java:63)
	at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
	at java.base/java.util.concurrent.CompletableFuture.uniWhenCompleteStage(CompletableFuture.java:883)
	at java.base/java.util.concurrent.CompletableFuture.whenComplete(CompletableFuture.java:2251)
	at java.base/java.util.concurrent.CompletableFuture.whenComplete(CompletableFuture.java:143)
	at

Hope that helps.

[FroMage]

This sounds like the problem is that Funqy doesn't run on a Vert.x context, no?

/cc @mkouba @cescoffier @patriot1burke @DavideD

[cescoffier]

Funqy is called on a duplicated context, but probably not marked as safe. Using @SafeVertxContext should fix the issue.