JS - JobScheduler
  1. JS - JobScheduler
  2. JS-1842

JobScheduler Master should support database access with Java 12

    Details

      Description

      Current Situation

      • The Master supports use of Java 8, 9,10 and 11 with a number of DBMS products e.g. MySQL 5.7, 8.0 and Microsoft SQL Server 2008, 2017.
      • When using JobScheduler Master for Windows 64bit, Java 12 then a Null Pointer exception is raised:
        • For example: use of a MySQL database 8.0 with MariaDB JDBC Driver 2.6.6:
          08 18:57:54.321 scheduler    0  8424.22F0 2793.020MB .{scheduler.service} SetServiceStatus SERVICE_START_PENDING
          08 18:57:54.368 scheduler   47  8424.22F0 2793.020MB .{scheduler} Cluster: switch_subsystem_state loaded
          08 18:57:54.368 scheduler    0  8424.22F0 2793.020MB ..{scheduler} Cluster: state=loaded
          08 18:57:54.368 scheduler    0  8424.22F0 2793.020MB .{scheduler} Web_services: switch_subsystem_state loaded
          08 18:57:54.368 scheduler    0  8424.22F0 2793.020MB ..{scheduler} Web_services: state=loaded
          08 18:57:54.368 scheduler    0  8424.22F0 2793.020MB ..[xc.insert 1, "java.lang.NullPointerException"]
          08 18:57:54.368 scheduler    0  8424.22F0 2793.020MB ..[xc.insert 2, "newInstance"]
          08 18:57:54.368 scheduler    0  8424.22F0 2793.020MB ..[xc.insert 3, "org.mariadb.jdbc.Driver"]
          08 18:57:54.368 scheduler    0  8424.22F0 2793.020MB .~Sos_database_session()   id=spooler db=jdbc:mysql://minos:3380/test_scheduler_1_12 user=scheduler cmd= open_mode=3 ref=0
          08 18:57:54.368 scheduler    0  8424.22F0 2793.020MB .Exception SCHEDULER-309  Error when opening database: Z-JAVA-105  Java exception java.lang.NullPointerException, method=newInstance [org.mariadb.jdbc.Driver]
          08 18:57:54.368 scheduler    0  8424.5E8  2794.020MB {scheduler.service} pending_watchdog_thread terminates
          08 18:57:54.368 scheduler    0  8424.22F0 2793.020MB .{scheduler.service} SetServiceStatus SERVICE_PAUSED
          
        • For example: use of a Microsoft SQL Server 2017 database with Microsoft JDBC Driver 7:
          08 18:25:05.838 scheduler    0  4156.21F0 2777.430MB .{scheduler.service} SetServiceStatus SERVICE_START_PENDING
          08 18:25:05.885 scheduler   46  4156.21F0 2778.461MB .{scheduler} Cluster: switch_subsystem_state loaded
          08 18:25:05.885 scheduler    0  4156.21F0 2778.461MB ..{scheduler} Cluster: state=loaded
          08 18:25:05.885 scheduler    0  4156.21F0 2778.461MB .{scheduler} Web_services: switch_subsystem_state loaded
          08 18:25:05.885 scheduler    0  4156.21F0 2778.461MB ..{scheduler} Web_services: state=loaded
          08 18:25:05.932 scheduler   47  4156.21F0 2774.605MB ..[xc.insert 1, "java.lang.NullPointerException"]
          08 18:25:05.932 scheduler    0  4156.21F0 2774.605MB ..[xc.insert 2, "newInstance"]
          08 18:25:05.932 scheduler    0  4156.21F0 2774.605MB ..[xc.insert 3, "com.microsoft.sqlserver.jdbc.SQLServerDriver"]
          08 18:25:05.932 scheduler    0  4156.21F0 2774.605MB .~Sos_database_session()   id=spooler db=jdbc:sqlserver://bacchus:1417;sendStringParametersAsUnicode=false;selectMethod=cursor;databaseName=test_scheduler_1_12 user=scheduler cmd= open_mode=3 ref=0
          08 18:25:05.932 scheduler    0  4156.21F0 2774.605MB .Exception SCHEDULER-309  Error when opening database: Z-JAVA-105  Java exception java.lang.NullPointerException, method=newInstance [com.microsoft.sqlserver.jdbc.SQLServerDriver]
          08 18:25:05.932 scheduler    0  4156.21F0 2775.605MB .{scheduler.service} SetServiceStatus SERVICE_PAUSED
          08 18:25:05.932 scheduler    0  4156.2284 2775.605MB {scheduler.service} pending_watchdog_thread terminates
          08 18:25:05.932 scheduler    0  4156.F18  2774.605MB {scheduler.service} Self destruction in 35 seconds, without further notice ...
          
        • Similar behavior applies when using an Oracle DBMS.
        • This problem does not occur when using Java 8, 9 10, 11 with the same databases.

      Desired Behavior

      • The Master should work with Java 12 when using the indicated databases and JDBC Drivers.

      Maintainer Notes

      • At the time of General Availability of JobScheduler release 1.12.9 no JDBC Driver compatible to Java 12 is available.
      • The above mentioned errors are raised by the JDBC Driver, not by JobScheduler Master.
      • The JobScheduler Master is technically compatible with Java 12, however, as there is no support for Java 12 from DBMS vendors we strongly discourage use of Java 12 before availability of compatible JDBC Drivers.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Andreas Püschel
              Reporter:
              Andreas Püschel
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: