Grpc and quarkus

[Casillas0905]

HI
In the new update of quarkus (3.9.4), has been any changes related to grpc services?
I'm trying to update to quarkus 3.9.4 from 3.2.10.Final, and i'm getting errors for the grpc service, this it what it says: io.grpc.StatusRuntimeException: UNAVAILABLE: io exception.
If anyone know anything i would appreciate it

[quarkus-bot[bot]]

/cc @alesj (grpc), @cescoffier (grpc)

[Emanuel-Rad]

Hi @cescoffier,

I'm @Casillas0905 's colleague. The issue seems to be that during testing, the gRPC client is trying to call on the default 9001 port, instead of the one specified. The setup is as follows:

(1) we have a docker container running with our @GrpcService MyService
(2) in a separate library, we have this class that should make a gRPC call to (1):

public class MyHandler {

    @GrpcClient
    MyService myService;

    public boolean call(...)
    {
        return myService.call(...)..await()...;
    }
}

(3) The test setup is as follows:

• the docker container (1) is started using testcontainers, that means that the exposed port is random - let's say 65315
• The quarkus.grpc.clients.myService.port property is set to 65315 using System.setProperty() in a QuarkusUnitTest
• The MyHandler from (2) is injected and called
• The call fails because it's trying to contact the docker container (1) on the default port 9001, instead of 65315
  Here's some snippets of the test:

public class MyTest {

    public static final GenericContainer myGrpcServerContainer = new GenericContainer(DockerImageName.parse("XXX:latest"))
            .withExposedPorts(5000); // we remapped the default 9000 gRPC port to 5000

    @RegisterExtension
    static final QuarkusUnitTest unitTest = new QuarkusUnitTest()
        .setBeforeAllCustomizer(() -> {
            myGrpcServerContainer.start();
            String port= myGrpcServerContainer.getMappedPort(5000).toString();   // this returns the 65315
            System.setProperty("quarkus.grpc.clients.myService.port", port);
        })
        .setArchiveProducer(() -> ShrinkWrap.create(JavaArchive.class)
                .addAsResource("mytest.properties", "application.properties");
        );

    @Inject
    MyHandler myHandler;

    @ParameterizedTest
    @ValueSource(strings = { "Foo", "Bar", "Invalid", "" })
    void MyHandlerTest(String role)
    {
        assertEquals(true, myHandler.call(...));
    }
}

[cescoffier]

Is MyHandler a gRPC client? Can you show the application config?

[cescoffier]

Also, was this approach working before?

[Emanuel-Rad]

MyHandler is just an ApplicationScoped bean, a wrapper class for the gRPC client inside (MyService). And yes, this worked with Quarkus 3.2.10.Final.

I managed to find a fix. Somewhere between Quarkus 3.2 and 3.8, a new config key was added: "test-port" (can't find any documentation about it tho). Switching from:
System.setProperty("quarkus.grpc.clients.myService.**port**", port);
to
System.setProperty("quarkus.grpc.clients.myService.**test-port**", port);
fixed the problem.

Do you know why this config was introduced? There are already a few other ways to change the port between prod and test, why add yet another way to do it?

[cescoffier]

Oh, this was always there but it did not work because of a bug. In tests, you need test-port, which means you can have your gRPC service in dev mode and test mode simultaneously.