[jboss-jira] [JBoss JIRA] (WFLY-11352) WildFly registers multiple distinct drivers for current MySQL driver jar

[Stephen Fikes (Jira)]

    [ https://issues.jboss.org/browse/WFLY-11352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669714#comment-13669714 ] 

Stephen Fikes commented on WFLY-11352:
--------------------------------------

It would be helpful to create the *first* driver just as if there were only one (without adding any suffix to the name) and create the second driver using the current strategy (I think appending _<fqc> to the driver jar name>? In this way, things would work out of the box (without anything unusual needing to be done) for the majority of users and those using the second driver would find it works just as it does now (they'd need to figure out the name and add it). This would represent a behavior change (though, likely a reasonable one) for anyone who has already worked around the issue using the suffixed driver name (the first workaround) instead of using one of the other workarounds mentioned above.

People are starting to use more recent MySQL drivers so problems are likely to become more common moving forward.

> WildFly registers multiple distinct drivers for current MySQL driver jar
> ------------------------------------------------------------------------
>
>                 Key: WFLY-11352
>                 URL: https://issues.jboss.org/browse/WFLY-11352
>             Project: WildFly
>          Issue Type: Bug
>          Components: JCA
>    Affects Versions: 14.0.1.Final
>            Reporter: Stephen Fikes
>            Assignee: Stefano Maestri
>            Priority: Major
>
> When MySQL drivers are deployed as jars (rather than [modules|https://issues.jboss.org/browse/WFLY-3218]), multiple named drivers:
> ... INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
> ... INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)
> ... INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.44-bin.jar_com.mysql.jdbc.Driver_5_1
> ... INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.44-bin.jar_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
> Consequently, references to the driver by name (such as the below) fail to resolve
> {code}
>                 <datasource jndi-name="java:jboss/datasources/mysql" pool-name="MySQL" enabled="true">
>                     ...
>                     <driver>mysql-connector-java-5.1.44-bin.jar</driver>
>                     ...
>                 </datasource>
> {code}
> This issue was [already resolved|https://issues.jboss.org/browse/WFLY-3218] for the case where a module was used to deploy the driver.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)