These various exceptions should have another "Caused by" exception
underneath. "Failed to frame message" always includes an additional cause
<https://github.com/grpc/grpc-java/blob/v1.13.2/core/src/main/java/io/grpc/internal/MessageFramer.java#L142-L153>
.

On Wed, Aug 1, 2018 at 7:44 PM <[email protected]> wrote:

> We are using salesforce's reactor-grpc and that is what the original
> client stack trace is from. I tested with a client using the standard
> blocking stub and below is the stack trace. Thanks
>
> Exception in thread "main" io.grpc.StatusRuntimeException: INTERNAL:
> Failed to frame message
> at io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:222)
> at io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:203)
> at io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:132)
> at
> com.deepintent.common.protobuf.WESGrpc$WESBlockingStub.fetchEntities(WESGrpc.java:381)
> at com.deepintent.client.Client.main(Client.java:143)
>
> On Wednesday, August 1, 2018 at 7:05:40 PM UTC-4, Carl Mastrangelo wrote:
>>
>> What is ErrorCallbackNotImplemented ?    There should be a cause included
>> in our exception.
>>
>> On Monday, July 30, 2018 at 4:18:45 PM UTC-7, [email protected]
>> wrote:
>>>
>>> Sure, here it is. The request message has a single string field.
>>>
>>> io.grpc.internal.SerializingExecutor run
>>> SEVERE: Exception while executing runnable
>>> io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed@f8594c1
>>> reactor.core.Exceptions$ErrorCallbackNotImplemented:
>>> io.grpc.StatusRuntimeException: INTERNAL: Failed to frame message
>>> Caused by: io.grpc.StatusRuntimeException: INTERNAL: Failed to frame
>>> message
>>> at io.grpc.Status.asRuntimeException(Status.java:526)
>>> at
>>> io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:419)
>>> at
>>> io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
>>> at
>>> io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
>>> at
>>> io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
>>> at
>>> io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose(CensusStatsModule.java:684)
>>> at
>>> io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
>>> at
>>> io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
>>> at
>>> io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
>>> at
>>> io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose(CensusTracingModule.java:391)
>>> at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:471)
>>> at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:63)
>>> at
>>> io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:553)
>>> at
>>> io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$600(ClientCallImpl.java:474)
>>> at
>>> io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:591)
>>> at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
>>> at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
>>> at
>>> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135)
>>> at
>>> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
>>> at java.base/java.lang.Thread.run(Thread.java:844)
>>>
>>> On Monday, July 30, 2018 at 6:15:09 PM UTC-4, Carl Mastrangelo wrote:
>>>>
>>>> Can you include the full stack trace?
>>>>
>>>> On Monday, July 30, 2018 at 10:17:45 AM UTC-7, [email protected]
>>>> wrote:
>>>>>
>>>>> Additionally, this happens on both grpc-java 1.12 and 1.13.2.
>>>>>
>>>>> On Monday, July 30, 2018 at 1:10:37 PM UTC-4, [email protected]
>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I am trying to debug a situation where I have 3 GRPC services using
>>>>>> the GRPC java. Each of the projects is a submodule of the parent maven
>>>>>> project and I'm using java 10. 1 of my services has stopped working and 
>>>>>> the
>>>>>> client error is saying io.grpc.StatusRuntimeException: INTERNAL: Failed 
>>>>>> to
>>>>>> frame message.
>>>>>>
>>>>>> I can include the protobuf file if it will help, but it's not a super
>>>>>> complex interface. If anyone has any ideas on what additional steps I 
>>>>>> could
>>>>>> take to debug, I would appreciate it. I am super confused on why 2 of 
>>>>>> the 3
>>>>>> services still work, and if I implement the interface in 1 of the other
>>>>>> projects, the interface works correctly. The pom file of the 2 submodules
>>>>>> are identical.
>>>>>>
>>>>>> Thanks in advance,
>>>>>> Rickey
>>>>>>
>>>>> --
> 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].
> Visit this group at https://groups.google.com/group/grpc-io.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/grpc-io/7dc2bd2f-aa4f-423d-b527-2e0ce6c12b2e%40googlegroups.com
> <https://groups.google.com/d/msgid/grpc-io/7dc2bd2f-aa4f-423d-b527-2e0ce6c12b2e%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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].
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CA%2B4M1oPHNXDU-HpVD6zybL-hy9HjDWuFjdeSyHn73naUK%2BgBQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to