Hi,
Can anyone tell me where to look for all possible exceptions thrown by grpc
server/client?
Maximum time I have seen below exception:
io.grpc.StatusRuntimeException: INTERNAL: HTTP/2 error code: INTERNAL_ERROR
Received Goaway
Above exception doesn't give clarity about what could have happene
On Thursday, October 4, 2018 at 12:51:33 AM UTC+10, natha...@skeyecode.com
wrote:
>
> Hello,
>
>
> I have some issues setting up grpc++ and Opencensus.
>
> Before anything else, I have built grpc_opencensus_plugin(and its
> dependencies) with Cmake. Could I have missed something regarding some ki
Yup, looks like you were right about the concurrent access as it throws
another exception when trying to remove from the HashSet thanks!
--
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
You looks like you were right about the concurrent access as it throws
another exception when trying to remove from the HashSet thanks!
--
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,
yes, you can call ManagedChannelBuilder.executor() and
ServerBuilder.executor(). I don't have any examples off hand, but we
personally prefer using ForkJoinPool as our executor.
On Thursday, October 4, 2018 at 8:06:48 AM UTC-7, cr2...@gmail.com wrote:
>
> Should have added I'm only interested o
(speaking on my own behalf, rather than the team): You can assume this
part of the API will never change. The usage of that API is widespread
enough that it would be infeasible to change it now, even if we reserved
the right to.
If you are keen on using a Non experimental API, you can use
Take it with a grain of salt since I'm not part of the gRPC team, but I
will answer to the best of my understanding.
If you have multiple gRPC streaming RPCs on the same channel, it will all
be multiplexed over the same connection. Using a non-streamed RPC per
instrument has a bigger overhead.
I think technically, the while (await requestStream.MoveNext()) on your
server side could also throw an exception if the client stream throws an
exception. But since all Tasks seems to be awaited and since you get back
in the while loop, this shouldn't be the problem. My best guess is that any
Should have added I'm only interested on the client side .. and this Java :)
On Thursday, October 4, 2018 at 11:03:02 AM UTC-4, cr2...@gmail.com wrote:
>
> Hi -
> Can an application override the managment of the thread/pools that grpc
> uses ? API ? any examples ?
> Thanks !
>
--
You receive
Hi -
Can an application override the managment of the thread/pools that grpc
uses ? API ? any examples ?
Thanks !
--
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
Hi,
we are about to create a service which receives subscription requests from
various clients. Each client can subscribe to price updates for specific
instruments.
The question we are facing now is whether it is better to have one rpc call
which gets a set of instruments (say 1000) as input an
This doesn't look like a problem with gRPC itself.
The RpcException: Status(StatusCode=Unknown, Detail="Exception was thrown
by handler.") only happens if the handler code (written by you) throws an
exception. Under normal circumstances, handlers should not do that and if
they the you as the aut
The libgrpc_csharp_ext.x64.so is that size because it is unstripped and
contains debug symbols (we keep the debug symbols because they make it much
easier to diagnose an issue in case of a grpc problem)
$ file libgrpc_csharp_ext.x64.so
libgrpc_csharp_ext.x64.so: ELF 64-bit LSB shared object x86
I have a simple C++ grpc client that talks to a grpc echo server written in
Go via a bidir stream. The messages that are sent back and forth are binary
blobs around 200 bytes in size.
On the C++ client side, I have a reader thread and a writer thread. The
reader sits in a loop and calls a block
14 matches
Mail list logo
