Anyone has any idea about the potential cause? On Tuesday, July 19, 2016 at 3:43:40 PM UTC-7, [email protected] wrote: > > 1.2 millions protos, and the total serialized data is a few GB I think. > The client thread is blocked here > >> - waiting on <0x7552c6db> (a >> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) >> - locked <0x7552c6db> (a >> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) >> at sun.misc.Unsafe.park(Native Method) >> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) >> at >> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) >> at >> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) >> at >> io.grpc.stub.ClientCalls$ThreadlessExecutor.waitAndDrain(ClientCalls.java:499) >> at >> io.grpc.stub.ClientCalls$BlockingResponseStream.waitForNext(ClientCalls.java:421) >> at >> io.grpc.stub.ClientCalls$BlockingResponseStream.hasNext(ClientCalls.java:434) > > > > On Tuesday, July 19, 2016 at 3:28:37 PM UTC-7, Eric Anderson wrote: >> >> On Tue, Jul 19, 2016 at 12:20 PM, ran.bi via grpc.io < >> [email protected]> wrote: >> >>> I don't think that is the problem in my case. >>> My server is basically like >>> >>> for all data >>> stream.onNext(data) >>> stream.onComplete() >>> >>> I don't see any chance to cause the problem you described. >>> >> >> Hmm... How much data are we talking here (total)? What version of >> grpc-java are you using? >> >
-- 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 post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/8b93d81a-3d9d-4c98-af5f-ebee40bc59af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
