-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Native build fails with oracle drivers and kogito together #19121
Comments
/cc @evacchi, @mariofusco |
I haven't looked at the code, but from looking at the error message it would seem that we need to patch @evacchi is that something you could look into? A system property which initializes a |
thanks @mariofusco :) |
hello, any news @mariofusco? |
Is this still an issue with the latest versions of Quarkus and Kogito? |
I have not done any testing recently (the POC that was using kogito, which we were doing in Sept/Oct, was considered finished and put on shelf). in the work I am doing now, there is no kogito anymore. |
Is this still an issue with the latest Quarkus versions? |
We have no pressing need for this at this Time. We can close if you want. |
No need to close if it's still an issue with the latest Quarkus versions |
Describe the bug
I am using kogito and oracle in the same application.
The build fails with:
Error: Detected a MBean server in the image heap. This is currently not supported, but could be changed in the future. Management beans are registered in many global caches that would need to be cleared and properly re-built at image build time. Class of disallowed object: com.sun.jmx.mbeanserver.JmxMBeanServer To see how this object got instantiated use --trace-object-instantiation=com.sun.jmx.mbeanserver.JmxMBeanServer. The object was probably created by a class initializer and is reachable from a static field. You can request class initialization at image runtime by using the option --initialize-at-run-time=<class-name>. Or you can write your own initialization methods and call them explicitly from your main entry point.
I have tried different combination of options, which worked:
--initialize-at-run-time=oracle.jdbc.datasource.impl.OracleDataSource
this looks similar to #19055, where the oracle driver has negative effects on other quarkus supported modules.
Expected behavior
Build passes.
Actual behavior
How to Reproduce?
Create an application with:
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
21.1.0 Java 11 CE (Java Version 11.0.11+8-jvmci-21.1-b05)
Quarkus version or git rev
2.1.0.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: