> There were plenty of messages processed for few days, and all of a sudden this exception breaks the connection.
Is it possible some new clients (esp clients using another gRPC language) are now connecting which is why you are seeing this error? > What does it mean, and how can be solved? Can you enable debug/trace logging to see the value of the "grpc-encoding" header for the offending RPC? That will give us some idea whether you need to use a custom decompressor registry. On Monday, January 23, 2023 at 9:41:17 PM UTC-8 chris...@gmail.com wrote: > Hello Everyone, > > We got this error on the server-side of a bi-di streaming: > > 2023-01-23 23:41:54,879 ERROR [GRPC worker, id #1] > io.grpc.netty.shaded.io.grpc.netty.NettyServerStream$TransportState > deframeFailed > WARNING: Exception processing message > io.grpc.StatusRuntimeException: INTERNAL: Can't decode compressed gRPC > message as compression not configured > at io.grpc.Status.asRuntimeException(Status.java:526) > at > io.grpc.internal.MessageDeframer.getCompressedBody(MessageDeframer.java:428) > at > io.grpc.internal.MessageDeframer.processBody(MessageDeframer.java:410) > at > io.grpc.internal.MessageDeframer.deliver(MessageDeframer.java:275) > at > io.grpc.internal.MessageDeframer.request(MessageDeframer.java:161) > at > io.grpc.internal.AbstractStream$TransportState$1RequestRunnable.run(AbstractStream.java:236) > at > io.grpc.netty.shaded.io.grpc.netty.NettyServerStream$TransportState$1.run(NettyServerStream.java:202) > at > io.grpc.netty.shaded.io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164) > at > io.grpc.netty.shaded.io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472) > at > io.grpc.netty.shaded.io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384) > at > io.grpc.netty.shaded.io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) > at > io.grpc.netty.shaded.io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) > at java.lang.Thread.run(Thread.java:748) > > > There were plenty of messages processed for few days, and all of a sudden > this exception breaks the connection. What does it mean, and how can be > solved? > > Is there a way to trap and "swallow" such exception so that the channel > does not get closed? > > Using grpc netty shaded 1.42.1 with epoll. > > Regards, > Chris > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/9f04e6f6-e555-4acd-93bd-58d15938f8c9n%40googlegroups.com.
