View FAQ Tags
We currently accept the following payment methods:
Debit or Credit Cards: To pay with your credit or debit card, please choose the PayPal payment method in our eshop. We use PayPal to process all bank card transactions.
Please note that you do not have to have a PayPal account to pay with your debit or credit card through PayPal. After you have been redirected to PayPal, select the Pay with a debit or credit card option, fill in your bank card details and click Pay. You can refer to the picture below.
PayPal Balance: If you have a PayPal account, you can use this option to pay quickly and easily. Please choose the PayPal payment method in our online eshop and after being redirected to the PayPal checkout page, select the Pay with my PayPal account option, fill in your PayPal login credentials and log in. You can refer to the picture below.
Wire Transfer: You can make a quick and safe bank wire transfer payment any time you need. Upon receiving your order, we will send you a pro-forma invoice with payment details (amount due, our bank account details) for you to realize your payment. Upon receiving your payment, we will send you the final invoice and license keys.
We do not offer this sort of guarantee at the moment. On the other had, we offer 30-day free fully-functional trial licenses for all of our paid QuartzDesk editions. During the 30-day trial period we provide full technical support.
We encourage our customers to try and evaluate QuartzDesk before they decide to make a purchase.
If you need more time to evaluate our products, feel free to request a new trial license once your current trial license expires. No questions asked.
Starting with QuartzDesk release 1.6.0, the QuartzDesk Public API library (quartzdesk-api-x.y.z.jar) source code is freely available and can be redistributed without any restrictions. The source code can be downloaded from the Maven Central repository and it is not available for download on our website.
The QuartzDesk Web Application (quartzdesk-web-x.y.z.war) and QuartzDesk JVM Agent (quartzdesk-agent-x.y.z.jar) source code is available only to selected OEM partners who wish to re-brand and re-distribute QuartzDesk as a part of their own product offering.
If you wish to receive detailed information on our OEM partnership program, please send an inquiry to email@example.com.
We provide three QuartzDesk editions - Lite, Standard and Enterprise. The Lite edition is free and the other two editions are paid.
For details on features available in individual QuartzDesk editions, please refer to our Pricing & Licensing Terms page.
We provide significant discounts to Startups, Open-Source Projects, Academia and Non-Profit Organizations. For details, please refer to the Pricing & Licensing Terms page.
Besides the above mentioned discounts, we also offer quantity and promotional discounts. Please use our online chat or write to firstname.lastname@example.org to discuss your requirements and the currently running promotions.
All non-free QuartzDesk edition licenses come automatically with 12 months of SW Maintenance that includes unlimited technical support and free product upgrades.
Once the SW Maintenance period is over, your software remains fully functional, but you will not be able to upgrade it nor will you be eligible to receive any technical support.
You can renew your SW Maintenance anytime for a highly discounted price. 30 days prior to your your SW Maintenance expiry, we will send an email notification message to the registered email address associated with your license key. For further details, please refer to our Pricing & Licensing Terms page.
SW Maintenance entitles you to download and install all fixes, updates and new product versions and to receive technical support. SW Maintenance is available only for non-free QuartzDesk editions (i.e. the Standard and Enterprise edition).
SW Maintenance has to be renewed every year and amounts to roughly 45% of the license costs.
All new non-free QuartzDesk edition license purchases initially come with 12 months of SW Maintenance. After the SW Maintenance expires, you can decide to keep the currently installed version or to purchase another year of SW Maintenance.
SW Maintenance for your license(s) can be renewed on this page. You will need to enter serial number(s) of licenses whose SW Maintenance you wish to renew.
The license serial number uses the XXXX-XXXX-XXXX-XXXX format and it is available in your license.key file - see the value of the serial-number element. Alternatively, the serial number can be obtained from a running QuartzDesk Web Application - see Help > License > Serial Number.
We will automatically notify you via email three times prior to the SW Maintenance expiry date. The email includes a unique link that you can use to renew SW Maintenance for all affected licenses.
Upon completing of the renewal process, you will receive replacement license keys with extended SW Maintenance. You must discard the old (replaced) license keys at the earliest possible date.
You can renew your SW Maintenance anytime. The new SW Maintenance will start as follows:
(1) If you renew after the expiry of your current SW Maintenance, then your new SW Maintenance will start on the expiry date of your current SW Maintenance and finish 12 months after the expiry date of your current SW Maintenance.
(2) If you renew before the expiry of your current SW Maintenance, then your new SW Maintenance will start on the renewal date and finish 12 months after the expiry date of your current SW Maintenance.
The version number can be obtained from the QuartzDesk JVM Agent log file.
... [2014-04-09 10:13:41,912] I [main] [com.quartzdesk.agent.Agent:405] - Initializing JVM Agent: com.quartzdesk.agent.Agent@1f3785d3 [QuartzDesk JVM Agent v1.5.0] ... [2014-04-09 10:13:47,318] I [main] [com.quartzdesk.agent.Agent:277] - Successfully initialized JVM Agent: com.quartzdesk.agent.Agent@1f3785d3 [QuartzDesk JVM Agent v1.5.0], enabled: true ...
Alternatively, the version number can be be obtained from the QuartzDesk JVM Agent distribution JAR file. Open the JAR file as a ZIP archive (you may need to temporarily rename the JAR file from *.jar to *.zip) and open the META-INF/MANIFEST.MF file.
Manifest-Version: 1.0 Ant-Version: Apache Ant 1.8.1 Created-By: Apache Maven Archiver-Version: Plexus Archiver Built-By: honza Build-Jdk: 1.6.0_43 Agent-Class: com.quartzdesk.agent.Agent Build-Date: 2014-03-25 Build-Number: 112 Implementation-Title: quartzdesk-agent Implementation-Vendor: QuartzDesk.com Implementation-Vendor-Id: com.quartzdesk Implementation-Vendor-URL: http://www.quartzdesk.com Implementation-Version: 1.5.0 Premain-Class: com.quartzdesk.agent.Agent
QuartzDesk supports all Quartz scheduler versions starting with Quartz 1.8.6 up to the latest Quartz 2.2.1.
I see "com.mysql.jdbc.PacketTooBigException: Packet for query is too large (xxxx > yyyy)..." error in the agent log.
This exception can occur when the agent attempts to store an execution history record in the quartzdesk_agent DB. It typically happens when the agent tries to store a record with a large (>500KB) job execution log.
To fix this error, you will need to adjust the value of the max_allowed_packet variable in your MySQL server configuration. The max_allowed_packet is measured in bytes and its new value should be large enough to accomodate the largest of your job execution logs produced by your jobs.
To determine the new max_allowed_packet value, you can extract the relevant error messages from your QuartzDesk JVM Agent log files using the following command:
grep "max_allowed_packet" *.log
In the output that contains a list of "Packet for query is too large (xxxx > yyyy)..." errors, search for the line with the biggest xxxx number. Set the max_allowed_packet variable to a number that is 10-20% bigger than the biggest found xxxx number.
Yes. The QuartzDesk Web Application has been designed to run on clusters. Please refer to the Cluster Deployment Notes chapter in the QuartzDesk Installation and Deployment Guide for cluster deployment details.
Please that you only need a single license to deploy the QuartzDesk Web Application to a cluster regardless of the number of cluster members.
The version number is displayed in the upper right-hand corner of a running QuartzDesk Web Application.
The version number is also displayed in the About window (Help -> About) opened from a running QuartzDesk Web Application.
Alternatively, the version number can be be obtained from the QuartzDesk Web Application distribution WAR file. Open the WAR file as a ZIP archive (you may need to temporarily rename the WAR file from *.war to *.zip) and open the META-INF/MANIFEST.MF file.
Manifest-Version: 1.0 Implementation-Title: quartzdesk-web Implementation-Version: 1.5.0 Class-Path: lib/quartzdesk-api-1.5.0.jar ... Built-By: honza Created-By: Apache Maven Build-Date: 2014-03-25 Implementation-Vendor: QuartzDesk.com Implementation-Vendor-URL: http://www.quartzdesk.com Implementation-Vendor-Id: com.quartzdesk Build-Jdk: 1.6.0_43 Main-Class: Launcher Archiver-Version: Plexus Archiver
The installed edition is displayed in the upper right-hand corner of a running QuartzDesk Web Application.
The installed edition is also displayed in the About window (Help -> About) opened from a running QuartzDesk Web Application.
Alternatively, the edition can be obtained from the installed license key file used by the QuartzDesk Web Application. Open the license.key file in the configured QuartzDesk Web application work directory.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ns2:license xmlns:ns2="http://license.quartzdesk.com/v1_0"> <serial-number>1</serial-number> <issue-date>2013-05-28+02:00</issue-date> <type>PERPETUAL</type> <licensee> <name>Test License</name> </licensee> <issuer> <name>CN=QuartzDesk.com CA2, O=QuartzDesk</name> <email>email@example.com</email> <web>www.quartzdesk.com</web> <certificate>-----BEGIN CERTIFICATE----- MIID9jCCAt6gAwIBAgIBAjANBgkqhkiG9w0BAQUFADAxMRMwEQYDVQQKEwpRdWFy ... 7cwIppIYwyMAmw== -----END CERTIFICATE----- </certificate> </issuer> <products> <product id="QuartzDesk"> <name>QuartzDesk Enterprise Edition</name> <edition>Enterprise</edition> <version> <major>1</major> </version> <feature-set id="Quartz"> ... </feature-set> </product> </products> <signature>...</signature> </ns2:license>
The one-step installation mode allows you to get QuartzDesk up and running within a minute by following these steps:
In the one-step installation mode QuartzDesk is started using an embedded Jetty servlet container / HTTP server and H2 database. The H2 database is automatically created and initialized in the QuartzDesk work directory upon application startup.
You can tweak the application web context name (default is /quartzdesk) and port number (default is 8080) using the following parameters specified at the end of the command line used to start the application:
The one-step installation mode is meant to be used solely for experimental and evaluation purposes. We advice against using this mode for any other purpose, e.g. for production deployments.
Q: When opening a scheduler connection I am getting a "QuartzDesk JVM Agent not detected, some of the QuartzDesk features will be disabled" warning. What does it mean?
When you see this warning it means the QuartzDesk JVM agent has either not been installed on the JVM the scheduler connection is opened to, or the JVM agent has been installed, but has been disabled using its
The QuartzDesk JVM Agent is required by some of the advanced QuartzDesk features. When the JVM agent is not available, these features cannot be used and are disabled in the QuartzDesk GUI. When this happens, you see the following message in the GUI.
Steps to fix the problem:
Q: When opening a scheduler connection I am getting a "Detected QuartzDesk JVM Agent (a.b.c) and QuartzDesk (x.y.z) version mismatch." warning. What does it mean?
When you see this warning it means there is a mismatch between the version of the installed QuartzDesk web-application and the QuartzDesk JVM agent installed on the JVM the scheduler connection is opened to.
To function properly, QuartzDesk requires a major and minor version number match. For example, if you are running QuartzDesk 1.4.0, then the QuartzDesk JVM Agent installed on the connected JVM must have a major version number of 1 and minor version number of 4.
Steps to fix the problem:
Q: When opening a scheduler connection I am getting a "Detected QuartzDesk JVM Agent (abc) and QuartzDesk (xyz) edition mismatch." warning. What does it mean?
When you see this warning it means there is incompatibility between the QuartzDesk web-application license edition and the license edition used by the QuartzDesk JVM Agent installed on the JVM the scheduler connection is opened to.
To function properly, QuartzDesk web-application requires the QuartzDesk JVM Agent to use a matching, or higher license edition. For example, if you are running the QuartzDesk web-application using the Standard edition license, then the QuartzDesk JVM Agent edition license must be either Standard, or Enterprise.
Steps to fix the problem:
Q: The Statistics panel says "No statistics data is available for the selected period". What does it mean?
When you see this message, it means the statistics data has not been generated yet.
It can be caused by either of the following reasons:
Of course you can!
QuartzDesk Web Application uses an embedded Quartz 2.x scheduler to execute various internal jobs. This Quartz scheduler is just like any other Quartz scheduler and you can manage it as long as a remote JMX connection can be established with the JVM QuartzDesk Web Application is running on. For details on how to enable remote JMX connections with a JVM, please refer to chapter "Enabling Remote JMX Access" of the How to Enable Remote JMX Access to Quartz Schedulers document.
If you need the advanced QuartzDesk features, then you will need to install the QuartzDesk JVM Agent on the JVM the QuartzDesk Web Application is running on. For details, please refer to the QuartzDesk JVM Agent Installation And Upgrade Guide document.
Q: Why do I have to edit the scheduler connection and click Discover button after I have restarted my Quartz enabled application?
This is because you have org.quartz.scheduler.instanceId=AUTO in your Quartz scheduler configuration and have not set org.quartz.scheduler.instanceIdGenerator.class configuration property. The value of the property must be a fully-qualified class name of an org.quartz.spi.InstanceIdGenerator implementation that you want to use to generate Quartz scheduler instance IDs.
Unless you have instructed Quartz to use a specific instance ID generator class, Quartz uses the org.quartz.simpl.SimpleInstanceIdGenerator class that generates pseudo-random instance IDs that change after every Quartz scheduler restart. This explains why you have to "re-discover" your schedulers when your Quartz-enabled application gets restarted.
Quartz distribution comes with the following suitable InstanceIdGenerator implementations: