jdbc | Please note the project | DB Client library

You need to establish a connection to SQL Server using JDBC driver and create JDBC URL in order to access table in Azure SQL server.

For more information, please check Establish connectivity to SQL Server.

Update: Version 1.6.9 has been released and should fix this issue! 🎉

This is actually a known bug, which is now open for quite a while: OSSRH-66257. There are two known workarounds:

As a workaround, use --add-opens to give the library causing the problem access to the required classes:

Your title says you are using Java 9. With Activiti 6 you will have to use JDK 1.8 (Java 8).

Seems like you are using Docker. If so you need to make sure that adal4j.jar is included in driver Docker container or it was added via --jars flag in Spark submit command:

You are using the default traceback logger of pytest, which also logs the arguments passed to a specific function. One way to solve this kind of leak is to use another traceback mode. You can find the general documentation at this link. In that link you can find two interesting traceback modes:

• --tb=short
• --tb=native

Both give you all the information you need during your specific test since:

• They still give you information about the tests failed or succeded
• Since you are using parametrized tests, the logs about failures will look like FAILED test_issue.py::test_connectivity[server_name-server_jdbc_port-server_database-name_env_credentials-name_env_pwd], in this way you can identify the actual failing test

Mind that this solution, while avoiding to log the credentials used at test time, these credentials used during testing must not be the same that will be used outside the test environment. If you are concerned with the fact that in case of failures in production, the logger could leak your credentials, you should setup you logger accordingly and avoid to log the default text of the exception.

Update: These issues have been fixed, and a patched version of jdeps is available as part of the early access build for JDK 18 at: http://jdk.java.net/18/ (starting from build 26)

Turning my comments into an answer. There seem to be 3 bugs going on here:

1. The MultiReleaseException seems to be because jdeps can not handle classes in different jars that have the same name, such as module-info.class, but are stored in a different META-INF/versions/xxx directory. (JDK-8277165)
2. The fact that this exception is sometimes suddenly not occuring seems to be the result of a race condition in the code that checks for the above; classes of the same name having multiple versions. (JDK-8277166)
3. The MultiReleaseException is missing it's exception message since it's thrown as part of an asynchronous task, which wraps it in an ExecutionException, which then leads to jdeps not reporting the exception correctly. (JDK-8277123)

As for a workaround, I don't think there's a good one at this point, except maybe for editing all the jars on the class path so that they put the module-info.class in the same META-INF/versions/xxx directory (but, this might have other consequences as well, so you probably don't want to run with the edited jars, and only use them for jdeps).

Your first excerpt is missing the important point:

Instead, virtual threads automatically give up (or yield) their carrier thread when a blocking call (such as I/O) is made. This is handled by the library and runtime [...]

The implication is this: if your code makes a blocking call into the library (for example NIO) the library detects that you call it from a virtual thread and will turn the blocking call into a non-blocking call, park the virtual thread and continue processing some other virtual threads code.

Only if no virtual thread is ready to execute will a native thread be parked.

Note that your code never calls a blocking syscall, it calls into the java libraries (that currently execute the blocking syscall). Project Loom replaces the layers between your code and the blocking syscall and can therefore do anything it wants - as long as the result for your calling code looks the same.

Probably the error is related to the migration from Oracle to Azure SQL Server.

As you can see in the source code of the library under the hood Spring Batch uses different strategies when generating the ids for jobs, job executions, and step executions.

In the Oracle case, they use sequences; with SQL Server, they implemented id generation using tables with an identity column.

The migration process also replicated the different Oracle sequences required by Spring Batch and very likely it is causing the issue when the aforementioned SQL Server id generation strategy tries obtaining the next value.

Please, drop the migrated sequences and create the three tables required for SQL Server with the appropriate values:

You should declare the scope of your jakarta.annotation dependency as provided: