Adding server grpc netty permit-keep-alive-time and permit-keep-alive-without-calls

[faculbsz-sg]

as configuration options

[quarkus-bot]

Thanks for your pull request!

The title of your pull request does not follow our editorial rules. Could you have a look?

• title should preferably start with an uppercase character (if it makes sense!)
• title should not start with chore/docs/feat/fix/refactor but be a proper sentence

This message is automatically generated by a bot.

[faculbsz-sg]

Hi, i am migrating a couple of plain grpc java services to use quarkus grpc.

Those services have some custom configurations that were recommended by grpc-java maintainers (grpc/grpc-java#8995) to solve a connection reset issue caused by the infrastructure where we are running our services (Google Cloud Run). We need to establish smaller keep alive values that netty server would allow, and indicate that they can be done when the service is not receiving any RPC call. For this we need to configure these 2 properties:

-permit keep alive time
-permit keep alive without calls

But unfortunately those options are not exposed by quarkus configuration, so after checking how the existing configurable option for the netty server was done (https://github.com/quarkusio/quarkus/pull/14957/files) i decided to do similar and open this pr.

Would you consider taking a look?

thanks!

[cescoffier]

Thanks! That's a nice addition!

[cescoffier]

Make sure you apply the formatter?

Can you build, and rebase?

[faculbsz-sg]

@cescoffier omw

[faculbsz-sg]

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  09:04 min
[INFO] Finished at: 2023-02-27T19:21:49+01:00

[faculbsz-sg]

@cescoffier could you merge it? or i should rebase

[cescoffier]

Can you squash the commits?

[faculbsz-sg]

Can you squash the commits?

done!

[quarkus-bot]

✔️ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.