...
- Since Java 9 Oracle® changed the JVM life cycle:
- New Java feature releases ship every 6 months.
- Public maintenance for Java feature releases is restricted to 6 months. Users can opt for a support contract with Oracle® to prolong maintenance for Java.
- Java releases do not follow semantic versioning.
- These changes affect JobScheduler releases as follows:
- We cannot know in advance if new Java releases will or will not be compatible with existing JobScheduler releases. Compatibility testing requires substantial effort and is partly performed by the JobScheduler community, see below explanations on Supported Compatibility 1) and Reported Compatibility 2).
- JobScheduler Agents are available for a larger number of platforms, including AIX®, HP-UX® etc. Such platforms tend to implement new JVM releases with some substantial delay.
- SOS Release Policies
- All JobScheduler components (Master, Agent, JOC Cockpit) are built with the same Java release.
- JobScheduler components are not built with the newest Java release but with the oldest compatible Java release, e.g. JobScheduler 1.12 and 2.0 are built with Java 1.8.
- We try to consider compatibility with newer Java feature releases, e.g. a JobScheduler Master 1.12.2 is built with Java 1.8 and can be operated with Java 1.8, 9 and 10 that are supported Java releases at the time of public availability of the JobScheduler Master. We do not guarantee compatibility with upcoming Java feature releases.
- For use of JobScheduler Long Term Support releases we encourage users to opt for a Java LTS release that provides maintenance for the same duration as JobScheduler LTS maintenance, see How long will you support the different versions of JobScheduler and YADE?
- We strive for compatibility of JobScheduler LTS releases with newer Java LTS releases, however, we do not check compatibility with individual Java feature release.
- We will not modify JobScheduler LTS releases to be built with newer Java versions. We will check to modify existing code to be compatible with the Java LTS release that has originally been used and with newer Java LTS releases, however, feasibility cannot be guaranteed as this depends on compatibility gaps between Java releases.
- For JobScheduler release 1.12 Java 1.8 is used for the build environment and Java 9,10, 11 can be used at run-time.
- JobScheduler is used with a DBMS product and vendor specific JDBC Drivers. Use of a specific DBMS and JDBC Driver limits the compatibility with specific Java releases. Check the DBMS Compatibility Matrix from the Which Database Management Systems are supported by JobScheduler? article.
JS7 JobScheduler Java Compatibility for Releases starting from 2.0
| JS7 JobScheduler Release | Java Runtime Environment | Java Build Environment | ||
|---|---|---|---|---|
| Supported Compatibility 1) | Reported Compatibility 2) | Supported Compatibility 1) | Reported Compatibility 2) | |
| JS7 Controller | ||||
| 2.0.0 | 1.8, 9, 10, 11, 12 | 1.8, 9, 10, 11, 12 | 1.8 | 1.8 |
| JS7 Agent | ||||
| 2.0.0 | 1.8, 9, 10, 11, 12 | 1.8, 9, 10, 11, 12 | 1.8 | 1.8 |
| JOC Cockpit | ||||
| 2.0.0 | 1.8, 9, 10 | 1.8, 9, 10 | 1.8 | 1.8 |
...