Server side streaming continues despite loss of client

39 views
Skip to first unread message

Robert Bielik

unread,
Jun 23, 2017, 1:44:51 AM6/23/17
to grpc.io
Hi,

I have a C++ client/server and an RPC where a progress message is sent back to the client. However, if the client dies unexpectedly, the server side keeps on
sending message without fail, i.e. writer->Write(msg) does not return false.

I'm using gRPC v1.0.1.

I build the server with grpc::ServerBuilder, and there is no explicit option set for it. Anything here I can do ?

Regards
/Robert

Nathaniel Manista

unread,
Jun 23, 2017, 12:14:43 PM6/23/17
to Robert Bielik, grpc.io
What you're saying smells to me like issue 11157 (never mind the Python/C++ distinction; the problem is suspected to be in shared code) although we're not aware of it having been introduced as early as 1.0.1.  Are you able to upgrade to a more recent version of gRPC and confirm your observations?
-Nathaniel

Nathaniel Manista

unread,
Jun 23, 2017, 12:43:26 PM6/23/17
to Robert Bielik, grp...@googlegroups.com
+the list (always retain the list unless you're sharing something truly private)

On Fri, Jun 23, 2017 at 9:34 AM, Robert Bielik <robert...@gmail.com> wrote:
I tried tag v1.4.0 right now, but CMake fails on a lib called "cares" ?

"You have called ADD_LIBRARY for library cares without any source files. This typically indicates a problem with your CMakeLists.txt file."

Is the CMake stuff up to par on v1.4.0 ?

Maybe; I'm not too familiar with that part of building gRPC but someone else certainly is (another reason to retain the list in the conversation).
-N

Nathaniel Manista

unread,
Jun 23, 2017, 12:59:36 PM6/23/17
to Robert Bielik, grp...@googlegroups.com
+the list

On Fri, Jun 23, 2017 at 9:57 AM, Robert Bielik <robert...@gmail.com> wrote:
It seems I was a bit too hasty. Always miss that submodule update thing... hrmf...

Glad to hear you're moving forward.
-N

Robert Bielik

unread,
Jun 24, 2017, 3:41:34 AM6/24/17
to Nathaniel Manista, grp...@googlegroups.com
It seems I was mistaken, the continued streaming was due to a future that didn't get cancelled properly, so the application was still running in the background. If I kill the app via taskmanager, the streaming stops from the server, just as expected. I've tried both v1.0.1 and v1.4.0.

Reply all
Reply to author
Forward
0 new messages