INTERNAL: Received unexpected EOS on empty DATA frame from server

[talipkorkmaz]

When I'm trying to call a stubbed GRPC method, Im taking a response like below.

2022-12-22 09:55:52.660 DEBUG 95520 --- [-worker-ELG-1-4] i.g.n.s.i.grpc.netty.NettyClientHandler  : [id: 0x3fed1b01, L:/127.0.0.1:51694 - R:localhost/127.0.0.1:5433] INBOUND WINDOW_UPDATE: streamId=0 windowSizeIncrement=983041
2022-12-22 09:55:52.660 DEBUG 95520 --- [-worker-ELG-1-4] i.g.n.s.i.grpc.netty.NettyClientHandler  : [id: 0x3fed1b01, L:/127.0.0.1:51694 - R:localhost/127.0.0.1:5433] INBOUND SETTINGS: ack=true
2022-12-22 09:55:52.667 DEBUG 95520 --- [-worker-ELG-1-4] i.g.n.s.i.grpc.netty.NettyClientHandler  : [id: 0x3fed1b01, L:/127.0.0.1:51694 - R:localhost/127.0.0.1:5433] OUTBOUND HEADERS: streamId=3 headers=GrpcHttp2OutboundHeaders[:authority: localhost:5433, :path: /user.UserContactDetailsService/getContactDetails, :method: POST, :scheme: http, content-type: application/grpc, te: trailers, user-agent: grpc-java-netty/1.48.1, grpc-accept-encoding: gzip, grpc-timeout: 2844557u] streamDependency=0 weight=16 exclusive=false padding=0 endStream=false
2022-12-22 09:55:52.671 DEBUG 95520 --- [-worker-ELG-1-4] i.g.n.s.i.grpc.netty.NettyClientHandler  : [id: 0x3fed1b01, L:/127.0.0.1:51694 - R:localhost/127.0.0.1:5433] OUTBOUND DATA: streamId=3 padding=0 endStream=true length=7 bytes=00000000020801
2022-12-22 09:55:52.734  INFO 95520 --- [p1680138169-325] WireMock                                 : Request received:
127.0.0.1 - POST /user.UserContactDetailsService/getContactDetails

content-type: [application/grpc]
te: [trailers]
user-agent: [grpc-java-netty/1.48.1]
grpc-accept-encoding: [gzip]
grpc-timeout: [2844557u]
host: [localhost:5433]

[aanbrn]

Trying to solve the same issue on my side, I've had to go deep into Spring Cloud Contract, WireMock and gRPC. Finally, I've prepared my own implementation of gRPC Verifier and Stub Configurer.

[marcingrzejszczak]

@aanbrn if you think that what we currently have is wrong please feel free to file a PR that improves the SCC implementation

[aanbrn]

@marcingrzejszczak ok, will do when have time.