Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GrpcService is not compatible with grpc server running on the same port as http #1048

Closed
fedinskiy opened this issue Feb 21, 2024 · 0 comments · Fixed by #1272
Closed

GrpcService is not compatible with grpc server running on the same port as http #1048

fedinskiy opened this issue Feb 21, 2024 · 0 comments · Fixed by #1272
Labels
priority/high higher priority than moderate but lower than urgent

Comments

@fedinskiy
Copy link
Contributor

When Quarkus run with GRPC, it complains about legacy GRPC support and recommends to disable a separate server with an option: quarkus.grpc.server.use-separate-server=false. If the option is added, grpc is accessible on the same port as http, ie it is described by variable quarkus.http.port and not by quarkus.grpc.server.port. Unfortunately, in such case our GRPC service still tries to access grpc port (eg: [1]) and fails.

[1] https://github.com/quarkus-qe/quarkus-test-framework/blob/main/quarkus-test-core/src/main/java/io/quarkus/test/services/quarkus/LocalhostQuarkusApplicationManagedResource.java#L101-L103

@fedinskiy fedinskiy changed the title GrpcService is not compatible with grpc server on the same port GrpcService is not compatible with grpc server running on the same port as http Feb 21, 2024
@michalvavrik michalvavrik added the priority/high higher priority than moderate but lower than urgent label May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/high higher priority than moderate but lower than urgent
Projects
None yet
2 participants