Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-26825

[GSS](7.4.z) war containing JDBC drivers deploys an extra driver


    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.4.17.CR1, 7.4.17.GA
    • 7.4.15.GA, 8.0 Update 1
    • JCA
    • None

      If a war has 2 jdbc drivers, it shows WFLYJCA0018 it starts :

      Which if you look in the web console under configuration datasources, you will see 3 drivers instead of 2 , technically the drivers.war one is the same as the mysql one.

      Typically jdbc jars should be deployed by themselves or put into a custom module. But it looks like we are also processing them if they are in a war (and probably also if an ear), if these drivers are usable, it looks like the drivers.war should not be started and just leave the other 2.

      This happens in EAP 7.4 and 8.0

      2024-03-01 21:16:09,623 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "drivers.war" (runtime-name: "drivers.war")
      2024-03-01 21:16:09,673 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on
      2024-03-01 21:16:09,842 INFO  [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.4.9.Final-redhat-00001 (Apache CXF 3.4.10.redhat-00001)
      2024-03-01 21:16:10,592 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry pdq.jar in /content/drivers.war/WEB-INF/lib/jcc-  does not point to a valid jar for a Class-Path reference.
      2024-03-01 21:16:11,518 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 8.0)
      2024-03-01 21:16:11,532 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0004: Deploying JDBC-compliant driver class com.ibm.db2.jcc.DB2Driver (version 4.32)
      2024-03-01 21:16:11,609 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = drivers.war_com.ibm.db2.jcc.DB2Driver_4_32
      2024-03-01 21:16:11,609 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = drivers.war
      2024-03-01 21:16:11,610 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = drivers.war_com.mysql.cj.jdbc.Driver_8_0 

            rhn-engineering-lgao Lin Gao
            rhn-support-vkamble Varsha Kamble
            0 Vote for this issue
            2 Start watching this issue