Change auto configs to use @Configuration(proxyBeanMethods = false)

[ST-DDT]

This should improve compatibility with GraalVM.

Fixes #379

@lthd92 Can you please verify whether this is all that needs to be done for GraalVM support?

[ST-DDT]

• TODO: Check for this.beanMethodCall()

[nickjn92]

This should improve compatibility with GraalVM.

Fixes #379

@lthd92 Can you please verify whether this is all that needs to be done for GraalVM support?

Will verify it later today 👍

[nickjn92]

This should improve compatibility with GraalVM.
Fixes #379
@lthd92 Can you please verify whether this is all that needs to be done for GraalVM support?

Will verify it later today +1

Successfully builds and start a native image built on a ubuntu system.

Instead of a 2-3 second startup time we now have:

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::                        

2020-07-16 23:24:11.097  INFO 2134349 --- [           main] .l.GraalGrpcSpringBootStarterApplication : Starting GraalGrpcSpringBootStarterApplication on x with PID 2134349 (/home/x/git/graalvm-grpc-starter/build/native/grpc-graal started by x in /home/x/git/graalvm-grpc-starter/build/native)
2020-07-16 23:24:11.097  INFO 2134349 --- [           main] .l.GraalGrpcSpringBootStarterApplication : No active profile set, falling back to default profiles: default
2020-07-16 23:24:11.193  INFO 2134349 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 2 endpoint(s) beneath base path '/actuator'
2020-07-16 23:24:11.198  WARN 2134349 --- [           main] i.m.c.i.binder.jvm.JvmGcMetrics          : GC notifications will not be available because MemoryPoolMXBeans are not provided by the JVM
2020-07-16 23:24:11.208  INFO 2134349 --- [           main] o.s.b.web.embedded.netty.NettyWebServer  : Netty started on port(s): 8080
2020-07-16 23:24:11.210  INFO 2134349 --- [           main] .l.GraalGrpcSpringBootStarterApplication : Started GraalGrpcSpringBootStarterApplication in 0.12 seconds (JVM running for 0.123)

[nickjn92]

This should improve compatibility with GraalVM.
Fixes #379
@lthd92 Can you please verify whether this is all that needs to be done for GraalVM support?

Will verify it later today +1

Successfully builds and start a native image built on a ubuntu system.

Instead of a 2-3 second startup time we now have:

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::                        

2020-07-16 23:24:11.097  INFO 2134349 --- [           main] .l.GraalGrpcSpringBootStarterApplication : Starting GraalGrpcSpringBootStarterApplication on x with PID 2134349 (/home/x/git/graalvm-grpc-starter/build/native/grpc-graal started by x in /home/x/git/graalvm-grpc-starter/build/native)
2020-07-16 23:24:11.097  INFO 2134349 --- [           main] .l.GraalGrpcSpringBootStarterApplication : No active profile set, falling back to default profiles: default
2020-07-16 23:24:11.193  INFO 2134349 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 2 endpoint(s) beneath base path '/actuator'
2020-07-16 23:24:11.198  WARN 2134349 --- [           main] i.m.c.i.binder.jvm.JvmGcMetrics          : GC notifications will not be available because MemoryPoolMXBeans are not provided by the JVM
2020-07-16 23:24:11.208  INFO 2134349 --- [           main] o.s.b.web.embedded.netty.NettyWebServer  : Netty started on port(s): 8080
2020-07-16 23:24:11.210  INFO 2134349 --- [           main] .l.GraalGrpcSpringBootStarterApplication : Started GraalGrpcSpringBootStarterApplication in 0.12 seconds (JVM running for 0.123)

However connection to the server doesnt seem to work. Getting

"error": "14 UNAVAILABLE: failed to connect to all addresses"

The actuator endpoints work fine which are running on netty 8080 but the actual grpc server which runs on 6080 is unable to handle receive requests

[ST-DDT]

Lets get this merged, as it improves startup times (a tiny bit) even without GraalVM native image.

---

I assume that this is caused by some missing configurations (reflection or alike).

The server doesn't show any logs related to the grpc server startup

gRPC Server started, listening on address: <address>, port: <port>

Maybe you have to use grpc-netty instead of grpc-netty-shaded?
The shaded dependency still refers to the non-shaded class names in the native-image configuration:

Args = --initialize-at-run-time=io.netty.buffer.PooledByteBufAllocator,io.netty.buffer.ByteBufAllocator[...]

I'll have a look at it later, when I finished some of the other issues for the current milestone.

[yidongnan]

LGTM