Details
-
Fix
-
Status: Released (View Workflow)
-
Blocker
-
Resolution: Fixed
-
1.13.4, 1.13.5
-
None
Description
Current Situation
- Use of newer Java releases e.g. after 1.8u251 (and similar for updates of newer Java branches) causes an incompatibility with the icu4j library (Unicode support) that ships with JOC Cockpit (icu4j-2.6.1.jar) and that prevents JOC Cockpit from starting.
- The problem can be observed from the JOC Cockpit log (./logs/yyyy-mm-dd.stderrout.log) like this:
java.lang.ExceptionInInitializerError at com.ibm.icu.impl.ICULocaleData.<clinit>(ICULocaleData.java:28) at com.ibm.icu.util.Calendar.setWeekCountData(Calendar.java:3670) at com.ibm.icu.util.Calendar.<init>(Calendar.java:1504) at com.ibm.icu.util.GregorianCalendar.<init>(GregorianCalendar.java:360) at com.ibm.icu.util.GregorianCalendar.<init>(GregorianCalendar.java:339) at com.ibm.icu.util.SimpleTimeZone.inDaylightTime(Simple
- This problem affects JOC Cockpit releases 1.13.4 and 1.13.5 only, earlier releases 1.13 are not affected. The same libraries are used for branch 1.12, however, for this branch the problem is not active.
Desired Behavior
An update to a current jaxen version 1.2.0 is required and the icu4j library is dropped from future releases. The icu4j library is just a transitive dependency that is imposed by the older jaxen version 1.1.1.
Workaround
- For the time being apply the workaround indicated with the below linked response provided with serverfault.com
Attachments
Issue Links
- relates to
-
JITL-626 Update jaxen-1.1.1 to jaxen-1.2.0 (dropping icu4j 2.6.1 that breaks Master plugins on startup)
-
- Released
-
- links to