ERROR - Failed to process event queue for client
See original GitHub issueReported by user Torran
on Discord.
I got a random error in my Teku logs, didn’t seem to affect its operation, should I be concerned?
ERROR - Failed to process event queue for client 902268355
java.util.concurrent.CompletionException: java.lang.IllegalStateException: s=OPEN,api=BLOCKED,sc=false,e=null
at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332) ~[?:?]
at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:347) ~[?:?]
at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:636) ~[?:?]
at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510) ~[?:?]
at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162) ~[?:?]
at tech.pegasys.teku.infrastructure.async.SafeFuture.lambda$propagateResult$3(SafeFuture.java:145) ~[teku-infrastructure-async-22.8.0.jar:22.8.0]
at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863) ~[?:?]
at java.util.concurrent.CompletableFuture.uniWhenCompleteStage(CompletableFuture.java:887) ~[?:?]
at java.util.concurrent.CompletableFuture.whenComplete(CompletableFuture.java:2325) ~[?:?]
at tech.pegasys.teku.infrastructure.async.SafeFuture.whenComplete(SafeFuture.java:576) ~[teku-infrastructure-async-22.8.0.jar:22.8.0]
at tech.pegasys.teku.infrastructure.async.SafeFuture.whenComplete(SafeFuture.java:32) ~[teku-infrastructure-async-22.8.0.jar:22.8.0]
at tech.pegasys.teku.infrastructure.async.SafeFuture.propagateResult(SafeFuture.java:142) ~[teku-infrastructure-async-22.8.0.jar:22.8.0]
at tech.pegasys.teku.infrastructure.async.SafeFuture.lambda$exceptionallyCompose$29(SafeFuture.java:395) ~[teku-infrastructure-async-22.8.0.jar:22.8.0]
at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863) ~[?:?]
at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841) ~[?:?]
at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510) ~[?:?]
at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162) ~[?:?]
at tech.pegasys.teku.infrastructure.async.SafeFuture.lambda$propagateResult$3(SafeFuture.java:145) ~[teku-infrastructure-async-22.8.0.jar:22.8.0]
at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863) ~[?:?]
at java.util.concurrent.CompletableFuture.uniWhenCompleteStage(CompletableFuture.java:887) ~[?:?]
at java.util.concurrent.CompletableFuture.whenComplete(CompletableFuture.java:2325) ~[?:?]
at tech.pegasys.teku.infrastructure.async.SafeFuture.whenComplete(SafeFuture.java:576) ~[teku-infrastructure-async-22.8.0.jar:22.8.0]
at tech.pegasys.teku.infrastructure.async.SafeFuture.whenComplete(SafeFuture.java:32) ~[teku-infrastructure-async-22.8.0.jar:22.8.0]
at tech.pegasys.teku.infrastructure.async.SafeFuture.propagateResult(SafeFuture.java:142) ~[teku-infrastructure-async-22.8.0.jar:22.8.0]
at tech.pegasys.teku.infrastructure.async.SafeFuture.propagateTo(SafeFuture.java:289) ~[teku-infrastructure-async-22.8.0.jar:22.8.0]
at tech.pegasys.teku.infrastructure.async.ScheduledExecutorAsyncRunner.lambda$createRunnableForAction$1(ScheduledExecutorAsyncRunner.java:119) ~[teku-infrastructure-async-22.8.0.jar:22.8.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
Caused by: java.lang.IllegalStateException: s=OPEN,api=BLOCKED,sc=false,e=null
at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:828) ~[jetty-server-9.4.48.v20220622.jar:9.4.48.v20220622]
at org.eclipse.jetty.server.HttpOutput.print(HttpOutput.java:1139) ~[jetty-server-9.4.48.v20220622.jar:9.4.48.v20220622]
at org.eclipse.jetty.server.HttpOutput.print(HttpOutput.java:1068) ~[jetty-server-9.4.48.v20220622.jar:9.4.48.v20220622]
at io.javalin.http.sse.Emitter.emit(Emitter.kt:29) ~[javalin-4.6.4.jar:4.6.4]
at io.javalin.http.sse.SseClient.sendEvent(SseClient.kt:29) ~[javalin-4.6.4.jar:4.6.4]
Aug 15 14:13:19 eth-node teku[407600]: at io.javalin.http.sse.SseClient.sendEvent$default(SseClient.kt:27) ~[javalin-4.6.4.jar:4.6.4]
at io.javalin.http.sse.SseClient.sendEvent(SseClient.kt) ~[javalin-4.6.4.jar:4.6.4]
at tech.pegasys.teku.beaconrestapi.handlers.v1.events.EventSubscriber.lambda$processEventQueue$1(EventSubscriber.java:121) ~[teku-data-beaconrestapi-22.8.0.jar:22.8.0]
at tech.pegasys.teku.infrastructure.async.SafeFuture.fromRunnable(SafeFuture.java:154) ~[teku-infrastructure-async-22.8.0.jar:22.8.0]
at tech.pegasys.teku.infrastructure.async.AsyncRunner.lambda$runAsync$0(AsyncRunner.java:23) ~[teku-infrastructure-async-22.8.0.jar:22.8.0]
at tech.pegasys.teku.infrastructure.async.SafeFuture.of(SafeFuture.java:73) ~[teku-infrastructure-async-22.8.0.jar:22.8.0]
... 4 more
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Queue is full, Server is too busy, clients cannot get their policies.
This can be caused if the Evtqueue is manually deleted and many files are currently processing. The database will have data on those...
Read more >Sentry stops processing when it receives too much events #859
After processing some event batches, it stops working. It works for about ~ 5 mins and then doesn't process new events. I tried...
Read more >Error "Failed to add message into clients message queue ...
Hello, We are having a weird problem. We developed an interface in ECC6, which produces 3 files. The files are downloaded by the...
Read more >Diagnosing and remedying stuck event processes - ServiceNow
Search for events process. Check if the Next action field is showing as future date/time and the State field is not queued or...
Read more >Manage the error queue when posts fail to process in Social ...
Click Setup; Go to Build | Customize | Social Media | Social Customer Service. Click the Error Log tab. In Salesforce Lightning: Click ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
ah, yeah ethereum-metrics-exporter hits the event stream pretty hard. There’s a good chance it wasn’t able to read the data being sent fast enough. Teku should handle this gracefully and disconnect it without the error but hopefully that gives us something to go on to try and reproduce this.
We’ve now updated Jetty and I’m no longer able to reproduce this.