4.2.0版本在用GraalVM时与HikariCP的兼容问题 #597

tuhe32 · 2023-11-27T09:13:44Z

Please fill it out carefully, or it will be closed.
请认真填写，不然会直接关闭。

Enviroment

Version info: 'GraalVM 22.3.0 Java 17 CE'
Java version info: '17.0.5+8-jvmci-22.3-b08'
C compiler: cc (apple, x86_64, 13.1.6)

JDK Version(required):
'17.0.5+8-jvmci-22.3-b08'
SpringBoot Version(required):
3.1.4
dynamic-datasource-spring-boot-starter Version(required):
4.2.0
druid Version(optional):

Describe what happened

项目用了HikariCP连接池
用mvn -Pnative clean native:compile 打包是成功的。启动报错：

Expected Result:

Actual Result:

If there is an exception,or aop invalid,please attach the exception trace:

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

2023-11-27T17:01:08.956+08:00  INFO 88353 --- [           main] c.e.bootnative.BootNativeApplication     : Starting AOT-processed BootNativeApplication using Java 17.0.5 with PID 88353 (/Users/liubin/work/projects/boot-native/target/boot-native started by liubin in /Users/liubin/work/projects/boot-native)
2023-11-27T17:01:08.956+08:00  INFO 88353 --- [           main] c.e.bootnative.BootNativeApplication     : No active profile set, falling back to 1 default profile: "default"
2023-11-27T17:01:08.971+08:00  INFO 88353 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.datasource.dynamic-com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceProperties' of type [com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-27T17:01:08.971+08:00  INFO 88353 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceAopConfiguration' of type [com.baomidou.dynamic.datasource.spring.boot.autoconfigure.DynamicDataSourceAopConfiguration$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-27T17:01:08.972+08:00  WARN 88353 --- [           main] c.b.d.d.support.DataSourceClassResolver  : Failed to init mybatis-plus support.
2023-11-27T17:01:08.972+08:00  INFO 88353 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'dsProcessor' of type [com.baomidou.dynamic.datasource.processor.DsJakartaHeaderProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-11-27T17:01:09.006+08:00  INFO 88353 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
2023-11-27T17:01:09.007+08:00  INFO 88353 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2023-11-27T17:01:09.007+08:00  INFO 88353 --- [           main] o.apache.catalina.core.StandardEngine    : Starting Servlet engine: [Apache Tomcat/10.1.13]
2023-11-27T17:01:09.020+08:00  INFO 88353 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2023-11-27T17:01:09.020+08:00  INFO 88353 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 64 ms
2023-11-27T17:01:09.034+08:00  WARN 88353 --- [           main] w.s.c.ServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'run': Unsatisfied dependency expressed through method 'run' parameter 0: Error creating bean with name 'bootNativeApplication.MyMapper': Cannot resolve reference to bean 'sqlSessionTemplate' while setting bean property 'sqlSessionTemplate'
2023-11-27T17:01:09.034+08:00  INFO 88353 --- [           main] o.apache.catalina.core.StandardService   : Stopping service [Tomcat]
2023-11-27T17:01:09.035+08:00 ERROR 88353 --- [           main] o.s.boot.SpringApplication               : Application run failed

org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'run': Unsatisfied dependency expressed through method 'run' parameter 0: Error creating bean with name 'bootNativeApplication.MyMapper': Cannot resolve reference to bean 'sqlSessionTemplate' while setting bean property 'sqlSessionTemplate'
	at org.springframework.beans.factory.aot.BeanInstanceSupplier.resolveArgument(BeanInstanceSupplier.java:317) ~[na:na]
	at org.springframework.beans.factory.aot.BeanInstanceSupplier.resolveArguments(BeanInstanceSupplier.java:260) ~[na:na]
	at org.springframework.beans.factory.aot.BeanInstanceSupplier.get(BeanInstanceSupplier.java:200) ~[na:na]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.obtainInstanceFromSupplier(DefaultListableBeanFactory.java:947) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.obtainFromSupplier(AbstractAutowireCapableBeanFactory.java:1214) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1158) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:560) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:520) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:325) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:323) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:973) ~[boot-native:6.0.12]
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:942) ~[boot-native:6.0.12]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:608) ~[boot-native:6.0.12]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:146) ~[boot-native:3.1.4]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:737) ~[boot-native:3.1.4]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:439) ~[boot-native:3.1.4]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) ~[boot-native:3.1.4]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1309) ~[boot-native:3.1.4]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1298) ~[boot-native:3.1.4]
	at com.example.bootnative.BootNativeApplication.main(BootNativeApplication.java:23) ~[boot-native:na]
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'bootNativeApplication.MyMapper': Cannot resolve reference to bean 'sqlSessionTemplate' while setting bean property 'sqlSessionTemplate'
	at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:377) ~[na:na]
	at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:135) ~[na:na]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1682) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1431) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:597) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:520) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:325) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:323) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:254) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1417) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1337) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:910) ~[na:na]
	at org.springframework.beans.factory.support.RegisteredBean.resolveAutowiredArgument(RegisteredBean.java:229) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.aot.BeanInstanceSupplier.resolveArgument(BeanInstanceSupplier.java:314) ~[na:na]
	... 21 common frames omitted
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'dataSourceScriptDatabaseInitializer': Unsatisfied dependency expressed through method 'dataSourceScriptDatabaseInitializer' parameter 0: Error creating bean with name 'dataSource': com.zaxxer.hikari.HikariConfig.<init>()
	at org.springframework.beans.factory.aot.BeanInstanceSupplier.resolveArgument(BeanInstanceSupplier.java:317) ~[na:na]
	at org.springframework.beans.factory.aot.BeanInstanceSupplier.resolveArguments(BeanInstanceSupplier.java:260) ~[na:na]
	at org.springframework.beans.factory.aot.BeanInstanceSupplier.get(BeanInstanceSupplier.java:200) ~[na:na]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.obtainInstanceFromSupplier(DefaultListableBeanFactory.java:947) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.obtainFromSupplier(AbstractAutowireCapableBeanFactory.java:1214) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1158) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:560) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:520) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:325) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:323) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:312) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:365) ~[na:na]
	... 36 common frames omitted
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource': com.zaxxer.hikari.HikariConfig.<init>()
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1770) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:598) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:520) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:325) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:323) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:254) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1417) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1337) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:910) ~[na:na]
	at org.springframework.beans.factory.support.RegisteredBean.resolveAutowiredArgument(RegisteredBean.java:229) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.aot.BeanInstanceSupplier.resolveArgument(BeanInstanceSupplier.java:314) ~[na:na]
	... 50 common frames omitted
Caused by: java.lang.NoSuchMethodException: com.zaxxer.hikari.HikariConfig.<init>()
	at [email protected]/java.lang.Class.getConstructor0(DynamicHub.java:3585) ~[boot-native:na]
	at [email protected]/java.lang.Class.getDeclaredConstructor(DynamicHub.java:2754) ~[boot-native:na]
	at com.baomidou.dynamic.datasource.toolkit.ConfigMergeCreator.create(ConfigMergeCreator.java:53) ~[na:na]
	at com.baomidou.dynamic.datasource.creator.hikaricp.HikariDataSourceCreator.createDataSource(HikariDataSourceCreator.java:75) ~[boot-native:na]
	at com.baomidou.dynamic.datasource.creator.DefaultDataSourceCreator.createDataSource(DefaultDataSourceCreator.java:97) ~[boot-native:na]
	at com.baomidou.dynamic.datasource.provider.AbstractDataSourceProvider.createDataSourceMap(AbstractDataSourceProvider.java:53) ~[boot-native:na]
	at com.baomidou.dynamic.datasource.provider.YmlDynamicDataSourceProvider.loadDataSources(YmlDynamicDataSourceProvider.java:53) ~[boot-native:na]
	at com.baomidou.dynamic.datasource.DynamicRoutingDataSource.afterPropertiesSet(DynamicRoutingDataSource.java:231) ~[boot-native:na]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1817) ~[boot-native:6.0.12]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1766) ~[boot-native:6.0.12]
	... 62 common frames omitted

Just paste your stack trace here!

Steps to reproduce

测试用例：

Step 1
测试用例地址
https://github.com/tuhe32/boot-native.git
Step 2
Step 3

The text was updated successfully, but these errors were encountered:

huayanYu · 2023-11-28T05:59:08Z

mvn -Pnative clean native:compile 跑不起来, 看异常感觉和classLoader有关...先自己排查看下也

linghengqian · 2023-11-28T07:16:04Z

Can you create a git of this zip at github.com so I can verify it via codespaces?
Please format your Error Log via markdown, which seems to be missing HikariCP’s GraalVM Reachability Metadata.

tuhe32 · 2023-11-28T08:12:34Z

Can you create a git of this zip at github.com so I can verify it via codespaces?

Please format your Error Log via markdown, which seems to be missing HikariCP’s GraalVM Reachability Metadata.

测试用例已经放到 git 上。https://github.com/tuhe32/boot-native.git
mvn -Pnative clean native:compile 是成功的。
启动项目时报错。

linghengqian · 2023-11-28T11:48:12Z

@tuhe32 Handled at linghengqian-scratches/boot-native@a58b8d9 .
It seems you don't know how to use org.springframework.boot:spring-boot-maven-plugin -- so I refactored the pom.xml and created two Maven Profile of nativeTest and generateMetadata to directly expose the Error Log.
You are using org.graalvm.sdk:graal-sdk at the classpath level, which is very dangerous behavior because the API of graal-sdk is not stable and its public API is usually used for Maven Plugin/Gradle Plugin/sbt Plugin. Please directly use JSON to define GraalVM Reachability Metadata, or use the relevant classes of Spring Framework to complete the definition of GraalVM Reachability Metadata. This additionally results in a buildArg that requires -H:+AllowDeprecatedBuilderClassesOnImageClasspath.
This appears to be a bug involving com.baomidou.mybatisplus.core.toolkit.LambdaUtils. What I mean is that Mybatis Plus doesn't seem to work under GraalVM Native Image. This commit also exposes that the Dynamic Datasource may be missing some JSON entries, but because of the issues with Mybatis Plus, I don't see the need to try to submit a PR.
Call @huayanYu , it looks like you are a committer for Mybatis Plus, do you have any more information?

Caused by: com.baomidou.mybatisplus.core.exceptions.MybatisPlusException: java.lang.ClassNotFoundException: com.example.bootnative.BootNativeApplication$$Lambda$0e4dae6cce3633a42432312a352810f4c99affcf
       com.baomidou.mybatisplus.core.toolkit.support.SerializedLambda.extract(SerializedLambda.java:58)
       com.baomidou.mybatisplus.core.toolkit.LambdaUtils.extract(LambdaUtils.java:67)
       com.baomidou.mybatisplus.core.conditions.AbstractLambdaWrapper.getColumnCache(AbstractLambdaWrapper.java:128)
       com.baomidou.mybatisplus.core.conditions.AbstractLambdaWrapper.columnToString(AbstractLambdaWrapper.java:66)
       com.baomidou.mybatisplus.core.conditions.AbstractLambdaWrapper.lambda$columnsToString$0(AbstractLambdaWrapper.java:57)
       [...]

linghengqian · 2023-11-28T12:18:39Z

Fixed in linghengqian-scratches/boot-native@50b6def , I just noticed com.example.bootnative.LambdaRegistrationFeature.🤣 I still would not encourage carrying GraalVM Feature classes on the classpath. This is very dangerous behavior with new versions of the GraalVM compiler.
In the reproduced git, I did not write additional extra-filter.json to filter the third-party library JSON. You can refer to https://github.com/baomidou/dynamic-datasource/blob/v4.2.0/native-image/extra-filter.json.
It looks like there are some JSON entries available for adding on the baomidou/dynamic-datasource side. @huayanYu Please assign this issue to me.

linghengqian · 2023-11-28T12:44:50Z

@tuhe32 I remove your custom graalvm featrue class via JSON at linghengqian-scratches/boot-native@8973788. Using graal-sdk is completely unreasonable, it shouldn't be on the classpath. lambdaCapturingTypes sets the GraalVM Reachability Metadata specific to your project. This seems to involve a bug in GraalVM CE 23.1.1 For JDK 21.0.1/GraalVM Tracing Agent, which does not collect the contents of lambdaCapturingTypes.

linghengqian · 2023-11-28T15:59:45Z

So I confirmed the real missing GraalVM Reachability Metadata at linghengqian-scratches/boot-native@34ff8ce. This question comes from https://github.com/oracle/graalvm-reachability-metadata/blob/0.3.5/metadata/com.zaxxer/HikariCP/5.0.1/reflect-config.json , not baomidou/dynamic-datasource .

[
  {
    "condition":{"typeReachable":"com.zaxxer.hikari.HikariConfig"},
    "name":"com.zaxxer.hikari.HikariConfig",
    "methods":[{"name":"<init>","parameterTypes":[] }]
  }
]

@tuhe32 I think you should open a related issue and PR at https://github.com/oracle/graalvm-reachability-metadata and provide a smaller unit test.
I don't think baomidou/dynamic-datasource should actively host HikariCP's GraalVM Reachability Metadata unless many people ask for it. @huayanYu What do you think?
This issue can be closed.

huayanYu · 2023-11-29T01:46:14Z

说实话,我完全不了解GraalVM.... mybatis-plus支持springboot3的相关issue baomidou/mybatis-plus#5527

linghengqian · 2023-11-29T04:07:13Z

There is a factual error in SpringBoot3支持问题 mybatis-plus#5527 (comment) , user should use JSON definition instead of introducing org.graalvm.sdk:graal-sdk, graal-sdk has been refactored starting with GraalVM 23.1.0, which means earlier versions of graal-sdk are completely obsolete.
The behavior of defining GraalVM Reachability Metadata for Mybatis through code does not involve conditional entries, which does not meet the requirements of GraalVM Reachability Metadata, which means that this class is incomplete in class introspection.
But in general, the current issue only concerns the missing GraalVM Reachability Metadata of HikariCP, which has nothing to do with Dynamic Datasource.

wssy001 · 2023-11-29T05:57:16Z

@linghengqian 引入 graal-sdk 纯属是无奈之举正如你前文提及的，Tracing Agent无法收集到lambdaCapturingTypes内容；而且Spring团队也不重视，之前有开发者提了feat，要求适配graal-sdk中org.graalvm.nativeimage.hosted.RuntimeSerialization#registerLambdaCapturingClass这一方法，结果还被当成了无意义提案。

linghengqian · 2023-11-29T06:04:59Z

@linghengqian 引入 graal-sdk 纯属是无奈之举正如你前文提及的，Tracing Agent无法收集到lambdaCapturingTypes内容；而且Spring团队也不重视，之前有开发者提了feat，要求适配graal-sdk中org.graalvm.nativeimage.hosted.RuntimeSerialization#registerLambdaCapturingClass这一方法，结果还被当成了无意义提案。

@wssy001 There is also no reason to use graal-sdk, I demonstrated it at linghengqian-scratches/boot-native@8973788 . Users only need to define json.

{
  "types":[
  ],
  "lambdaCapturingTypes":[
    {
      "name":"com.example.bootnative.BootNativeApplication"
    }
  ],
  "proxies":[
  ]
}

huayanYu · 2023-11-29T07:01:08Z

所以和动态数据源无关是吧.

linghengqian · 2023-11-29T07:06:51Z

所以和动态数据源无关是吧.

This issue has nothing to do with dynamic datasource unless we host the GraalVM Reachability Metadata of a third-party library like shardingsphere. Reference https://github.com/apache/shardingsphere/tree/3aff42fbe6909674d7582e098c9c1a453a63e86d/infra/reachability-metadata/src/main/resources/META-INF/native-image .
The JSON for these third-party libraries is more suitable for submission to https://github.com/oracle/graalvm-reachability-metadata . Users can add it by themselves.

huayanYu · 2023-11-30T02:01:47Z

不明觉厉,closed.

bob266 · 2023-12-08T09:41:08Z

所以和动态数据源无关是吧.

This issue has nothing to do with dynamic datasource unless we host the GraalVM Reachability Metadata of a third-party library like shardingsphere. Reference https://github.com/apache/shardingsphere/tree/3aff42fbe6909674d7582e098c9c1a453a63e86d/infra/reachability-metadata/src/main/resources/META-INF/native-image .

The JSON for these third-party libraries is more suitable for submission to https://github.com/oracle/graalvm-reachability-metadata . Users can add it by themselves.

在你的例子里面,可以跑起来,但是我要如何在编译的时候不报错呢

linghengqian · 2023-12-08T12:25:15Z

所以和动态数据源无关是吧.

This issue has nothing to do with dynamic datasource unless we host the GraalVM Reachability Metadata of a third-party library like shardingsphere. Reference https://github.com/apache/shardingsphere/tree/3aff42fbe6909674d7582e098c9c1a453a63e86d/infra/reachability-metadata/src/main/resources/META-INF/native-image .

The JSON for these third-party libraries is more suitable for submission to https://github.com/oracle/graalvm-reachability-metadata . Users can add it by themselves.

在你的例子里面,可以跑起来,但是我要如何在编译的时候不报错呢

@bob266 So my example proves that the error has nothing to do with Dynamic DataSource, but where is your example?

huayanYu closed this as completed Nov 30, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

4.2.0版本在用GraalVM时与HikariCP的兼容问题 #597

4.2.0版本在用GraalVM时与HikariCP的兼容问题 #597

tuhe32 commented Nov 27, 2023 •

edited

Loading

huayanYu commented Nov 28, 2023

linghengqian commented Nov 28, 2023 •

edited

Loading

tuhe32 commented Nov 28, 2023

linghengqian commented Nov 28, 2023

linghengqian commented Nov 28, 2023

linghengqian commented Nov 28, 2023

linghengqian commented Nov 28, 2023

huayanYu commented Nov 29, 2023

linghengqian commented Nov 29, 2023

wssy001 commented Nov 29, 2023 •

edited

Loading

linghengqian commented Nov 29, 2023

huayanYu commented Nov 29, 2023

linghengqian commented Nov 29, 2023

huayanYu commented Nov 30, 2023

bob266 commented Dec 8, 2023

linghengqian commented Dec 8, 2023

4.2.0版本在用GraalVM时与HikariCP的兼容问题 #597

4.2.0版本在用GraalVM时与HikariCP的兼容问题 #597

Comments

tuhe32 commented Nov 27, 2023 • edited Loading

Enviroment

Describe what happened

Steps to reproduce

huayanYu commented Nov 28, 2023

linghengqian commented Nov 28, 2023 • edited Loading

tuhe32 commented Nov 28, 2023

linghengqian commented Nov 28, 2023

linghengqian commented Nov 28, 2023

linghengqian commented Nov 28, 2023

linghengqian commented Nov 28, 2023

huayanYu commented Nov 29, 2023

linghengqian commented Nov 29, 2023

wssy001 commented Nov 29, 2023 • edited Loading

linghengqian commented Nov 29, 2023

huayanYu commented Nov 29, 2023

linghengqian commented Nov 29, 2023

huayanYu commented Nov 30, 2023

bob266 commented Dec 8, 2023

linghengqian commented Dec 8, 2023

tuhe32 commented Nov 27, 2023 •

edited

Loading

linghengqian commented Nov 28, 2023 •

edited

Loading

wssy001 commented Nov 29, 2023 •

edited

Loading