Here in Alberta, we'll now be staying with MDT on Nov 1st. Where can we pick up a Java update to support that? Seen articles on how to change TZ, but not the rules inside.
We’re running: JAVA_VERSION="17.0.15"
So we’ll need to install tzdata2026c ?
So, looks like a Java RT update then.
Thx, Ken
Hello @Ken Brown
Which Bitbucket and Java versions are you running? Alberta's new time zone rules are already included in IANA tzdata 2026c. Java 21.0.13 and 17.0.21 include these changes for America/Edmonton. For Bitbucket Data Center, update the Java runtime Bitbucket uses.
Changing -Duser.timezone alone won't update the underlying rules.
You can check the Java timezone data versions here.
Which Bitbucket and Java versions are you running?
Best, Arek 🤠🧙♂️
UpdateNo need to install tzdata2026c manually because 17.0.21 includes the updated Alberta timezone rules. Updating Bitbucket’s Java runtime and restart it. If that’s not possible, use Oracle’s TZUpdater tool to update timezone data.
Looks like: Atlassian Bitbucket v9.4.19
My Unix team tells me that Java is embedded in BitBucket, and they can't manage it. So the solution 'needs to come from the vendor'
And we've booked tonight to update it before Nov 1st.
Directing them to the TZupdater tool, which is run from where? It does say this in the link: To update timezone data successfully, you should ensure that you have sufficient privileges to modify the JDK_HOME/jre/lib or JRE_HOME/lib directory. If you do not have sufficient privileges to modify these directories, contact your system administrator.
JDK_HOME/jre/lib
JRE_HOME/lib
TZUpdater runs from the command line on your Bitbucket server, and not within Bitbucket itself. Your Unix team can check which Java installation Bitbucket uses in <BITBUCKET_INSTALL>/bin/set-jre-home.sh, then verify its timezone data version with: <JRE_HOME>/bin/java -jar /path/to/tzupdater.jar -V Be sure to stop Bitbucket before updating that runtime’s timezone data. I recommend installing Java 17.0.21 separately and pointing Bitbucket to it via set-jre-home.sh. It includes tzdata 2026c, and Atlassian supports external Java installations. You should also check OpenSearch's Java configuration.
Atlassian documentation: https://support.atlassian.com/bitbucket-data-center/kb/security-considerations-about-jre-versions-used-in-bitbucket-data-center/
TZUpdater instructions: https://www.oracle.com/java/technologies/javase/tzupdater-readme.html
Timezone data versions:https://ops.java/tzdata/
Not seeing set-jre-home.sh? [root@rhlbbp01 bin]# pwd /var/atlassian/application-data/bitbucket/bin [root@rhlbbp01 bin]# ls -l total 16 -rwxrwx---. 1 atlbitbucket atlbitbucket 321 Nov 12 2017 ask-pass.pl drwxrwx---. 2 atlbitbucket atlbitbucket 4096 Oct 17 2023 git-hooks drwxrwx---. 2 atlbitbucket atlbitbucket 4096 Oct 17 09:25 git-scripts -rwxrwx---. 1 atlbitbucket atlbitbucket 597 Nov 12 2017 ssh-git.bat
You're looking in the Bitbucket home directory, not the installation directory. 🙂 For Bitbucket 9.4.19, try this:
ls -l /opt/atlassian/bitbucket/9.4.19/bin/set-jre-home.sh
If it's installed elsewhere, your Unix team can locate it using:
find /opt/atlassian -name set-jre-home.sh 2>/dev/null
Just one more question before my upgrade tonight while you're still around. I got this from our Unix support and my plan:
I don't see anything were we need to set JRE_HOME or JAVA_HOME etc before running tzupdater.jar
No, you don't need to set JAVA_HOME or JRE_HOME as long as you run TZUpdater with the exact Java executable Bitbucket uses. Just be sure to stop Bitbucket, back up the Java runtime, apply and verify the update, and then restart Bitbucket.
https://www.oracle.com/java/technologies/javase/tzupdater-readme.html
It looks like you're new here. Sign in or register to get started.
