Cannot use mssql-jdbc 12.10 on WildFly if WildFly directory path contains a space

[dleborgne]

Driver version

12.10

SQL Server version

not important (issue occurs before connection)

Client Operating System

Windows 2016

JAVA/JVM version

Java 21.0.6

Problem description

On WildFly, any attempt to test a connection pool using Microsoft SQL Server JDBC drivers 12.10 will fail if WildFly installation path contains a space.
This is a regression from previous versions like 12.8.1 for instance.

Steps

1. Download WildFly 35.0.1
2. Extract to "C:\Program Files" (or any other directory path which contains a space)
3. Copy mssql-jdbc-12.10.0.jre11.jar to "C:\Program Files\wildfly-35.0.1.Final\standalone\deployments"
4. Start WildFly using "C:\Program Files\wildfly-35.0.1.Final\bin\standalone.bat"
5. Start JBoss CLI using "C:\Program Files\wildfly-35.0.1.Final\bin\jboss-cli.bat" --connect
6. Create a datasource using /subsystem=datasources/data-source=MyDataSource:add(jndi-name=java:jboss/resources/jdbc/MyDataSource,driver-name="mssql-jdbc-12.10.0.jre11.jar",connection-url="jdbc:sqlserver://mssql.company.com:1433")
7. Test datasource using /subsystem=datasources/data-source=MyDataSource:test-connection-in-pool()

Expected behavior

Connection is tested

Actual behavior

Unable to test connection

Error message/stack trace

java.net.URISyntaxException: Illegal character in path at index 15: vfs:/C:/Program Files/WildFly/wildfly-35.0.1.Final/bin/content/mssql-jdbc-12.10.0.jre11.jar
Complete error message and stack trace.

[MrEasy]

I am actually right now debugging it :) and can confirm this issue.

Problem is this change of #2579 which does not consider bundles and then errors out fatally, even though calling method #readFromFile has comments that point to this not intended.

Stack: error.log

[ecki]

(In @MrEasy ‘s case it is OSGi/Karaf not Wildfly but exceptions related to classpsth URL in the retry config). In the case of bundles it Happens always (regardless of Space).

BTW why is that Retry config using a separate config file/system anyway and how can its position been configured (Independent of the jar location which looks like a odd default).

[MrEasy]

fyi, following change avoids the error - better would be handling that is able to read from bundles as well.

Catch_error_on_trying_to_read_properties_from_bundle_location_(#2646).patch