FAQs

Frequently Asked Questions - public api

FAQs - public api
Q: When testing or opening a Quartz scheduler connection I am getting a "QuartzDesk Public API Library has not been detected on the Quartz scheduler's classpath." warning. What does it mean?

When you see this warning it means the QuartzDesk Public API Library JAR has not been installed on the Quartz scheduler's classpath as described in the QuartzDesk JVM Agent Installation and Upgrade Guide.

The QuartzDesk Public API Library connects the Quartz scheduler with the QuartzDesk JVM Agent. Without this connection, some of the advanced QuartzDesk features cannot function properly and are disbaled in the QuartzDesk GUI.

Steps to fix the problem:

  1. Edit the Quartz scheduler connection to see which JVM and Quartz scheduler instance the connection points to. The target JVM can be identified using the host and port. The Quartz scheduler instance can be identified using the Quartz scheduler object name.
  2. Make sure the QuartzDesk Public API Library JAR is installed on the Quartz scheduler's classpath and is loaded by the same classloader that loads the Quartz scheduler API (quartz-x.y.z.jar). For installation details, please refer to the QuartzDesk JVM Agent Installation And Upgrade Guide available for download in Installation And Upgrade Guides.
  3. Make sure there is only one QuartzDesk Public API Library JAR on the Quartz scheduler's classpath.
  4. Close the warning dialog and repeat the original action.
TAGS: detected, public api, public-api-not-detected
Q: When testing or opening a Quartz scheduler connection I am getting a "QuartzDesk Public API Library has not been installed correctly on the Quartz scheduler's classpath." warning. What does it mean?

When you see this warning it means the QuartzDesk Public API Library JAR is present on the Quartz scheduler's classpath, but it is not loaded by the same class loader that loads the Quartz scheduler API (quartz-x.y.z-jar).

Steps to fix the problem:

  1. Edit the Quartz scheduler connection to see which JVM and Quartz scheduler instance the connection points to. The target JVM can be identified using the host and port. The Quartz scheduler instance can be identified using the Quartz scheduler object name.
  2. Make sure the QuartzDesk Public API Library JAR is installed on the Quartz scheduler's classpath and is loaded by the same classloader that loads the Quartz scheduler API (quartz-x.y.z.jar). For installation details, please refer to the QuartzDesk JVM Agent Installation And Upgrade Guide available for download in Installation And Upgrade Guides.
  3. Make sure there is only one QuartzDesk Public API Library JAR on the Quartz scheduler's classpath.
  4. Close the warning dialog and repeat the original action.
TAGS: loaded, public-api-not-loaded-correctly
Q: When testing or opening a Quartz scheduler connection I am getting a "Detected QuartzDesk Public API Library (a.b.c) and QuartzDesk JVM Agent (x.y.z) versions mismatch." warning. What does it mean?

When you see this warning it means the version of the QuartzDesk Public API Library installed on the Quartz scheduler's classpath is not compatible with the version of the QuartzDesk JVM Agent installed on the JVM the Quartz scheduler connection points to.

Steps to fix the problem:

  1. Edit the Quartz scheduler connection to see which JVM and Quartz scheduler instance the connection points to. The target JVM can be identified using the host and port. The Quartz scheduler instance can be identified using the Quartz scheduler object name.
  2. Make sure the correct version of the QuartzDesk Public API Library is installed on the Quartz scheduler's classpath. At least the major and minor version numbers must match. For installation details, please refer to the QuartzDesk JVM Agent Installation And Upgrade Guide available for download in Installation And Upgrade Guides.
  3. Make sure there is only one QuartzDesk Public API Library JAR on the Quartz scheduler's classpath.
  4. Close the warning dialog and repeat the original action.
TAGS: library, public-api-incompatible-version, version, versions mismatch