Getting UNIMPLEMENTED with Java client and server with protobuff 3.4 and grpc 1.8.0

[Hrishi Joshi]

We have a java based gRPC server and client. Both using version 1.8.0.

After verifying both client and the server have the same proto file and java lib generated from the same proto, while client sending the request to server is getting 

```io.grpc.StatusRuntimeException: UNIMPLEMENTED: Method not found: package.Servicename/method

    at io.grpc.Status.asRuntimeException(Status.java:526)

    at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:418)

    at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:41)

    at io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose(CensusStatsModule.java:663)

    at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:41)

    at io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose(CensusTracingModule.java:392)

    at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:443)

    at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:63)

    at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:525)

    at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$600(ClientCallImpl.java:446)

    at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:557)

    at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)

    at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

    at java.lang.Thread.run(Thread.java:748)```

What may be happening wrong ? We checked almost everything that could be checked

1. gRPC version

2. protobuff version

3. proto file

4. Java lib from proto file

on both client and server and also

5. Server listening on the port after startup

We are currently clueless on what should be done next. Any pointers are appreciated.

Rishi

[Hrishi Joshi]

We found the solution ourselves. It was because of wrong package scan path