Investigate slowdown through `io.grpc` version increment

[smcvb]

Enhancement Description

Since axonserver-connector-java has incremented the io.grpc dependency from version 1.59.1 to version 1.65.1, we have noted slowdown within regular use of the connector (through for example Axon Framework).
We should investigate where the slowdown comes from and how we can resolve this.
Without resorting to a downgrade of the grpc-bom dependency.

Current Behaviour

Everything works with grpc-bom version 1.65.1, but there is a noticeable performance impact compared to version 1.59.1

Wanted Behaviour

Ensure the axonserver-connector-java does not have a performance penalty when using version 1.65.1 or higher of the grpc-bom dependency.

Possible Workarounds

Override the grpc-bom dependency to 1.59.1.

[adben002]

Could this be related to the protoc versions not aligning with the ones in the dependencies? Things like AbstractAsyncStub have been introduced by default into the generator.

With a change like:

axonserver-connector-java/pom.xml

Lines 332 to 337 in b95e707

	<configuration>
	<protocArtifact>com.google.protobuf:protoc:3.6.1:exe:${os.detected.classifier}</protocArtifact>
	<pluginId>grpc-java</pluginId>
	<pluginArtifact>io.grpc:protoc-gen-grpc-java:1.19.0:exe:${os.detected.classifier}</pluginArtifact>
	<protoSourceRoot>${project.build.directory}/proto</protoSourceRoot>
	</configuration>

⬇️

<configuration>
    <protocArtifact>com.google.protobuf:protoc:3.25.1:exe:${os.detected.classifier}</protocArtifact>
    <pluginId>grpc-java</pluginId>
    <pluginArtifact>io.grpc:protoc-gen-grpc-java:${grpc.version}:exe:${os.detected.classifier}</pluginArtifact>
    <protoSourceRoot>${project.build.directory}/proto</protoSourceRoot>
</configuration>

(btw, I found this when investigating if a dependent service could utilise protobuf v4)

[smcvb]

That's a worthy path to try out, @adben002! Thanks for sharing that nugget of info with us.

[smcvb]

For all reading this, both #404 and #405 work towards the suggested adjustment made by @adben002. The former is for the 2025 release of this connector, which will increase the JDK to 11. The latter is a patch release for 2024, thus still base-lined on JDK8.