You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Problem

The JOC Cockpit's user interface and the joc.log file can report an error message like this:

Error Message when accessing Notifications
2022-06-13T05:58:03,959 INFO  qtp1099855928-9546   c.s.j.c.JOCDefaultResponse                   -
REQUEST: ./xmleditor/read
PARAMS: {"controllerId":"jobscheduler","objectType":"NOTIFICATION"}
USER: root
2022-06-13T05:58:03,959 ERROR qtp1099855928-9546   c.s.j.c.JOCDefaultResponse                   - java.nio.file.NoSuchFileException: /var/sos-berlin.com/js7/joc/resources/joc/xsd/notification/Notification_configuration_v1.0.xsd
java.nio.file.NoSuchFileException: /var/sos-berlin.com/js7/joc/resources/joc/xsd/notification/Notification_configuration_v1.0.xsd

Analysis

Notifications are managed from the Configuration->Notification sub-view of JOC Cockpit.

  • The configuration format of notifications is XML. The JOC Cockpit offers an XSD schema-aware XML Editor for configuration purposes.
  • The XSD Schema file is added by the JOC Cockpit installer. 

  • If users previously created their own Docker volumes from earlier JOC Cockpit releases that did not include the XSD Schema then the JETTY_BASE/resources/joc/xsd directory might be missing. In fact the directory is included with the image but is not visible when an existing Docker volume is mounted to the JETTY_BASE/resources/joc directory.
    • This problem is limited to use of volumes with Docker containers.
    • This problem does not occur when installing JOC Cockpit on premises.

Solution

Download the XSD Schema from the indicated link and store the file to JETTY_BASE/resources/joc/xsd/notification/Notification_configuration_v1.0.xsd

If required create the xsd/notification directory in JETTY_BASE/resources/joc..



  • No labels