Helidon exceptions are not propagated up through PbjProtocolHandler to the application via onError
#304
Labels
Bug
An error that causes the feature to behave differently than what was expected based on design.
Description
An exception thrown in
io.helidon.common.buffers.ReadOnlyArrayData
invokes theonError()
method in PbjProtocolHandler but that method does not signal an error to the application layer viaFlow.Subscriber<? super Bytes> incoming
. This prevents the application layer from taking action and cleaning up, etc.Steps to reproduce
PbjProtocolHandler.onError()
method on the running server:pbj/pbj-core/pbj-grpc-helidon/src/main/java/com/hedera/pbj/grpc/helidon/PbjProtocolHandler.java
Lines 643 to 654 in a2e54fa
PbjProtocolHandler.onError()
method.incoming.onError()
or an equivalent to notify the application layer there was a problem.Additional context
This is an example of how
grpc.io
handles the same exception:Hedera network
No response
Version
v0.9.9
Operating system
macOS
The text was updated successfully, but these errors were encountered: