Legacy Knowledge Base
Published Sep. 10, 2025

How to check Java's TZData (Timezone Data) version

Written By

Gustavo Vasconcelos

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

In countries where Daylight Savings Time (Summer Time) is defined each year the timezone data (TZData) can be outdated. This procedure can help you fetch the version of the TZData currently in use in your Java Virtual Machine, which can be later cross-referenced with Oracle's or IANA's TZData official releases to check if an update is necessary.

 

Environment

  • Any Liferay Portal or DXP version.

 

Resolution

  • On the main portal instance, go to Control Panel > Configuration > Server Administration and the Script tab.
  • Paste the following Groovy script and click Execute.
String output = java.time.zone.ZoneRulesProvider.getVersions("UTC").lastEntry().getKey();
out.println( "Java vendor: " + System.getProperty("java.vendor"));
out.println( "Java version: " + System.getProperty("java.version"));
out.println( "TZData data file version: " + output ) ;
  • The output should be something like:
Java vendor: Azul Systems, Inc.1.8.0_282
Java version: 1.8.0_282
TZData data file version: 2020d

 

Additional Information

 

Did this article resolve your issue ?

Legacy Knowledge Base