Validation of license expiration date

Zing JVM requires a valid non-expired license file for launching Java applications. 

The license file is only checked during start of the Zing JVM process. That means the Zing JVM process will continue to run, even if it reaches through the expiration date and the hard-stop date.

As exact time for the expiration, the end of the day of the expiration date is used within the local timezone of the Zing JVM process.

Two dates are defining the license validity: The expiration date is the date written in the license contract between the customer and Azul. The hard-stop date is the date which technically limits the usability of the license. The hard-stop date allows to add some safety buffer after the expiration date to evade possible issues with false timezone calculations.

Since ZVM 18.07.0.0 the license validity can be checked with the following command:

/opt/zing/zing-jdk8/bin/java -version

To receive more detailed output, especially showing which license file is actually used by the process, run the following:

/opt/zing/zing-jdk8/bin/java -Xlog:license=debug -version

The expiration date can be extracted with the following command from the license file:

grep sublicense.expires /etc/zing/license

Further information about standard locations of license files and how to install the license file:
Installing a Zing License

Azul Support 24/7 email or phone, for contacting about any license issue: http://www.azul.com/support

 

Add Comment

Comments

0 comments

Please sign in to leave a comment.

Was this article helpful?
0 out of 0 found this helpful