Skip to content
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

Fatal error when running nativeTest with ojdbc 23.3.0.23.09 #7979

Open
radovanradic opened this issue Dec 7, 2023 · 3 comments
Open

Fatal error when running nativeTest with ojdbc 23.3.0.23.09 #7979

radovanradic opened this issue Dec 7, 2023 · 3 comments
Assignees

Comments

@radovanradic
Copy link
Member

Describe the issue
Looks like we started getting test to fail intermittently since upgrading to vertx-client-oracle 4.5.0 which requires Oracle ojdbc8 23.3.0.23.09. I have extracted an example from our larger test, but the execution and flow should be the same. However, it's not failing each time so not sure how hard will be to reproduce. Attached is example and logs that I extracted from one failure.

Steps to reproduce the issue
hibernate-reactive-oracle.zip

  1. Extract hibernate-reactive-oracle.zip
  2. ./gradlew nativeTest

Describe GraalVM and your environment:

  • GraalVM version Oracle GraalVM 21.0.1+12.1
  • JDK major version: 21
  • OS: Linux
  • Architecture: x64

More details
Here are error logs from the tests we got.
error.log

Based on logs, I assume this is the same as an old closed issue #2101 because vertx-oracle-client 4.5.0 that pulls Oracle ojdbc 23.3.0.23.09 and it has this code in class oracle.jdbc.driver.GeneratedPhysicalConnection in method getApplicationProgramName calling Thread.getAllStackTraces()

static String getApplicationProgramName(final String defaultValue) {
        return (String)AccessController.doPrivileged(new PrivilegedAction<String>() {
            public String run() {
                String sessionProgram = defaultValue;
                Collection<StackTraceElement[]> stacks = Thread.getAllStackTraces().values();
                ...

we have reactive tests and X number of threads accessing db so the test is failing randomly in GraalVM with the error reported in this issue.

Please note I did not get failure from the attached app but app was copied from the test module that fails randomly.

@christianhaeubl
Copy link
Member

Tracked internally as GR-50859.

@peter-hofer
Copy link
Member

@radovanradic , using your reproducer and steps to reproduce just gives me:

HibernateReactiveOracleTest > initializationError FAILED
    io.micronaut.context.exceptions.BeanInstantiationException at DefaultBeanContext.java:1980
        Caused by: io.micronaut.context.exceptions.BeanInstantiationException at DefaultBeanContext.java:2324
            Caused by: io.micronaut.testresources.client.TestResourcesException at TestResourcesClientPropertyExpressionResolver.java:130

I also get a report that says:

io.micronaut.context.exceptions.BeanInstantiationException: Bean definition [org.hibernate.SessionFactory] could not be loaded: Error instantiating bean of type  [org.hibernate.boot.SessionFactoryBuilder]

Message: Test resources service wasn't able to revolve expression 'jpa.default.properties.hibernate.connection.url': java.net.http.HttpTimeoutException: request timed out
...

@radovanradic
Copy link
Member Author

If you are running on Apple Silicon it may be issue with the docker. I need to use Colima for Oracle on Apple Silicon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants