Uploaded image for project: 'SET - Setups'
  1. SET - Setups
  2. SET-146

Setup should not fall back to MySQL driver class if a newer version of a JDBC Driver is specified

    XMLWordPrintable

    Details

    • Type: Fix
    • Status: Released (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.12.6
    • Labels:
      None

      Description

      Current Situation

      • If the JOC Cockpit setup is configured to use an individual JDBC Driver for a MySQL database then the setup creates hibernate files with the entry:
        <property name="hibernate.connection.driver_class">com.mysql.jdbc.Driver</property>
      • This configuration item is wrong as it defaults to use of a MySQL JDBC Driver. In fact this configuration item is generated by the setup when e.g. installing a newer version of the MariaDB JDBC Driver that would require the following configuration item:
        <property name="hibernate.connection.driver_class">org.mariadb.jdbc.Driver</property>
      • The JOC Cockpit setup is different from the JobScheduler Master setup that handles this situation flawlessly.

      Desired Behavior

      • JOC Cockpit should not default to use the MySQL Driver class if a newer version of a JDBC driver is used.

      Workaround

      • After installation of JOC Cockpit adjust the hibernate configuration files in ./jetty_base/resources/joc to specify the correct driver class.
      • By default the file names are jobscheduler.hibernate.cfg.xml and reporting.hibernate.cfg.xml

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                oh Oliver Haufe
                Reporter:
                ap Andreas Püschel
                Approver:
                Andreas Püschel
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: