You'll need to include a thread dump to diagnose this further. On Wednesday, June 19, 2019 at 8:52:54 PM UTC-7, Deepak Agarwal wrote: > > Hi all, > I am using grpc java as a grpc client to connect to a remote GRPC > server. The RPC is a server streaming RPC. > I first build the channel (have not provided customized executor), and > then invoke the RPC. > > Scenario: > 1. I have several destination servers where i have to connect. > 2. for one destination, the same RPC can be invoked multiple times (with > different parameters) > 3. The RPC is server streaming RPC. > > What did I do: > 1. I created one ManagedChannel(have not provided customized executor) for > each destination server. > 2. On the same ManagedChannel, i invoke multiple RPCs as and when > required, and the RPCs keeps running (server keeps on streaming) until user > stops the operation. > > Problem: > After few hours, i see there are many threads(in several hundreds) which > are spawn by the application and it keeps on increasing with time. > > PS: I don't have a thread dump. The thread leak was identified by some > external tool in production environment >
-- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/55bf968a-5a00-4975-8508-6aa615ec830d%40googlegroups.com.
