dimas-b opened a new issue, #3203: URL: https://github.com/apache/polaris/issues/3203
### Describe the bug * Run `RestCatalogFileIntegrationTest` * Observe error logged by [TaskExecutorImpl](https://github.com/apache/polaris/blob/64b13a9915274a04e82a12c9fdcd095d12797ca0/runtime/service/src/main/java/org/apache/polaris/service/task/TaskExecutorImpl.java#L150): ``` java.util.concurrent.CompletionException: jakarta.enterprise.context.ContextNotActiveException: RequestScoped context was not active when trying to obtain a bean instance for a client proxy of CLASS bean [class=org.apache.polaris.service.task.TaskFileIOSupplier, id=7kBDtfomB8MiW4C8Cl5bNPGxnxg] - you can activate the request context for a specific method using the @ActivateRequestContext interceptor binding at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315) at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run$$$capture(CompletableFuture.java:1807) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java) at --- Async.Stack.Trace --- (captured by IntelliJ IDEA debugger) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.<init>(CompletableFuture.java:1790) at java.base/java.util.concurrent.CompletableFuture.asyncRunStage(CompletableFuture.java:1818) at java.base/java.util.concurrent.CompletableFuture.runAsync(CompletableFuture.java:2033) at org.apache.polaris.service.task.TaskExecutorImpl.tryHandleTask(TaskExecutorImpl.java:145) at org.apache.polaris.service.task.TaskExecutorImpl.lambda$tryHandleTask$1(TaskExecutorImpl.java:151) at java.base/java.util.concurrent.CompletableFuture$UniComposeExceptionally.tryFire(CompletableFuture.java:1040) at java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482) at io.smallrye.context.impl.wrappers.SlowContextualRunnable.run(SlowContextualRunnable.java:19) at org.jboss.threads.EnhancedViewExecutor$EnhancedViewExecutorRunnable.run(EnhancedViewExecutor.java:496) at io.quarkus.vertx.core.runtime.VertxCoreRecorder$15.runWith(VertxCoreRecorder.java:650) at org.jboss.threads.EnhancedQueueExecutor$Task.doRunWith(EnhancedQueueExecutor.java:2651) at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2630) at org.jboss.threads.EnhancedQueueExecutor.runThreadBody(EnhancedQueueExecutor.java:1622) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1589) at org.jboss.threads.DelegatingRunnable.run(DelegatingRunnable.java:11) at org.jboss.threads.ThreadLocalResettingRunnable.run(ThreadLocalResettingRunnable.java:11) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.base/java.lang.Thread.run(Thread.java:1583) Caused by: jakarta.enterprise.context.ContextNotActiveException: RequestScoped context was not active when trying to obtain a bean instance for a client proxy of CLASS bean [class=org.apache.polaris.service.task.TaskFileIOSupplier, id=7kBDtfomB8MiW4C8Cl5bNPGxnxg] - you can activate the request context for a specific method using the @ActivateRequestContext interceptor binding at io.quarkus.arc.impl.ClientProxies.notActive(ClientProxies.java:76) at io.quarkus.arc.impl.ClientProxies.getSingleContextDelegate(ClientProxies.java:32) at org.apache.polaris.service.task.TaskFileIOSupplier_ClientProxy.arc$delegate(Unknown Source) at org.apache.polaris.service.task.TaskFileIOSupplier_ClientProxy.apply(Unknown Source) at org.apache.polaris.service.task.TableCleanupTaskHandler.handleTask(TableCleanupTaskHandler.java:96) at org.apache.polaris.service.task.TaskExecutorImpl.handleTask(TaskExecutorImpl.java:187) at org.apache.polaris.service.task.TaskExecutorImpl.handleTaskWithTracing(TaskExecutorImpl.java:226) at org.apache.polaris.service.task.TaskExecutorImpl.lambda$tryHandleTask$0(TaskExecutorImpl.java:146) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run$$$capture(CompletableFuture.java:1804) ... 20 more ``` ### To Reproduce _No response_ ### Actual Behavior _No response_ ### Expected Behavior _No response_ ### Additional context This is probably a side effect of #2974 ### System information _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
