Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-3333

Deploying a jdbc driver ignores the --name parameter in the cli

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Done
    • 8.0.0.Final, 8.1.0.CR1, 8.1.0.Final
    • 9.0.0.Beta1
    • JCA
    • None

    Description

      Hi,

      I'm in the process of migrating from 7.2.0 to 8.0.0Final. The command I use on the cli to deploy my jdbc drivers is :

      deploy <jarname> --name <driver-name>
      e.g. : deploy db2jcc4.jar --name=db2

      In 7.2.0, this would set the driver-name to db2. However, in wildfly this does not seem to work :

       
      8.0.0:
              {
                  "driver-name" => "db2_com.ibm.db2.jcc.DB2Driver_4_13",
                  "deployment-name" => "db2_com.ibm.db2.jcc.DB2Driver_4_13",
                  "driver-module-name" => undefined,
                  "module-slot" => undefined,
                  "driver-datasource-class-name" => undefined,
                  "driver-xa-datasource-class-name" => undefined,
                  "driver-class-name" => "com.ibm.db2.jcc.DB2Driver",
                  "driver-major-version" => 4,
                  "driver-minor-version" => 13,
                  "jdbc-compliant" => true
              }
      7.2.0:
              {
                  "driver-name" => "db2",
                  "deployment-name" => "db2",
                  "driver-module-name" => undefined,
                  "module-slot" => undefined,
                  "driver-datasource-class-name" => undefined,
                  "driver-xa-datasource-class-name" => undefined,
                  "driver-class-name" => "com.ibm.db2.jcc.DB2Driver",
                  "driver-major-version" => 4,
                  "driver-minor-version" => 13,
                  "jdbc-compliant" => true
              }
       

      Strangly enough, deploy -l on 8.0.0 gives me :

      NAME     RUNTIME-NAME ENABLED STATUS
      db2      db2          true    OK
      

      But when I try to define a datasource using this driver-name, I get :

      "JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.driver-demander.java:/architectuurDS is missing [jboss.jdbc-driver.db2]","jboss.data-source.java:/architectuurDS is missing [jboss.jdbc-driver.db2]"]}}
      

      When I use "db2_com.ibm.db2.jcc.DB2Driver_4_13" as driver-name, the datasource works normally. I'm assuming it has something to do with WFLY-1269 ... ?

      Is this a bug ? How do I get the driver to have the correct driver-name ?

      Thanks !

      Peter.

      Attachments

        Activity

          People

            smaestri@redhat.com Stefano Maestri
            peter.vanbiesen Peter Van Biesen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: