jinrongluo edited a comment on pull request #723: URL: https://github.com/apache/incubator-eventmesh/pull/723#issuecomment-1034198696
> I run the `AsyncPublishInstance` and `EventmeshAsyncSubscribe` under the `grpc` module, got following error: > > * Received Server side error: INTERNAL: gRPC frame header malformed: reserved bits not zero. >  > > After got this error, the client has been shutted down and only got one message, but the topic offset has been updated to 5, this phenomenon is reasonable ?  > > this error is not inevitable, please take a look, thanks. @jinrongluo Thanks @xwm1992 The root cause of this issue is that Grpc StreamObserver is not thread safe. The Java doc is here: https://grpc.github.io/grpc-java/javadoc/io/grpc/stub/StreamObserver.html ``` Since individual StreamObservers are not thread-safe, if multiple threads will be writing to a StreamObserver concurrently, the application must synchronize calls. ``` The fix is in this commit - https://github.com/apache/incubator-eventmesh/pull/723/commits/48ab8d36e2fafe959fe4db27fc6d644457dd55e6 -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
