It is not reliable to look in the add/remove programs menu in Windows, because Java is not always installed in this way. You can easily identify the version of Java that your TeamCity server is using in Administration | Diagnostics | Java Configuration. You can see the path to the Java in use in this menu as Java Home Path.
If you're running a TeamCity server that was installed using the Windows Installer, you are likely using the bundled Amazon Corretto located in <teamcity home directory>/jre. Otherwise, it is possible to define the Java to use by utilizing a few different options, described in detail in Install Non-Bundled Version of Java.
I found that our main TC server is using Java version: 1.8.0_211 Java VM info: Java HotSpot(TM) 64-Bit Server VM Java Home path: C:\Program Files\Java\jre1.8.0_211 Server: Apache Tomcat/9.0.75
which is odd since we keep seeing this message
This TeamCity server is using a deprecated version of Java (8). Please upgrade Java as future versions of TeamCity will be incompatible with Java 8.
Your Java version is 1.8.0_211, which is also known as Java 8. While Java 8 can still be used, the recommendation at this time is to upgrade your Java to either 11 or 17 because it will no longer be supported in a coming release.
It does look like you're not running a bundled version of Amazon Corretto, based on your Java Home path: C:\Program Files\Java\jre1.8.0_211. There are several environment variables that can be used to set this location, you could check each of them to see what you've configured on your system.
TEAMCITY_JRE
JRE_HOME
JAVA_HOME
TeamCity will use these in the listed order, with TEAMCITY_JRE taking the priority. Once you've installed the newer version of Java, you can update the environment variable with the new location and restart your TeamCity.
TeamCity itself runs within a JRE, but it is up to users to choose what Java they wish to use in their own environment.
Supported Java versions: OpenJDK and Oracle Java 8 (8u16 or later), 11, and 17 (32 or 64 bit). Using 64-bit Java is recommended.
The TeamCity server Windows installer and server Docker images come bundled with Amazon Corretto 64-bit Java 17.
For Apple ARM systems (for example, Apple M1 or M2), consider using a different version of Java, like Azul OpenJDK.
Awesome, thank you!
Here is what is installed on my server.
Is looking at Add/Remove programs a good way to tell which version of Java TC uses?
Or is there a config file I can look at?
Thanks
It is not reliable to look in the add/remove programs menu in Windows, because Java is not always installed in this way. You can easily identify the version of Java that your TeamCity server is using in Administration | Diagnostics | Java Configuration. You can see the path to the Java in use in this menu as Java Home Path.
If you're running a TeamCity server that was installed using the Windows Installer, you are likely using the bundled Amazon Corretto located in
<teamcity home directory>/jre
. Otherwise, it is possible to define the Java to use by utilizing a few different options, described in detail in Install Non-Bundled Version of Java.Thank you!
I found that our main TC server is using
Java version: 1.8.0_211
Java VM info: Java HotSpot(TM) 64-Bit Server VM
Java Home path: C:\Program Files\Java\jre1.8.0_211
Server: Apache Tomcat/9.0.75
which is odd since we keep seeing this message
This TeamCity server is using a deprecated version of Java (8). Please upgrade Java as future versions of TeamCity will be incompatible with Java 8.
Can you advise on this?
Thank you
Your Java version is 1.8.0_211, which is also known as Java 8. While Java 8 can still be used, the recommendation at this time is to upgrade your Java to either 11 or 17 because it will no longer be supported in a coming release.
It does look like you're not running a bundled version of Amazon Corretto, based on your Java Home path: C:\Program Files\Java\jre1.8.0_211. There are several environment variables that can be used to set this location, you could check each of them to see what you've configured on your system.
TeamCity will use these in the listed order, with TEAMCITY_JRE taking the priority. Once you've installed the newer version of Java, you can update the environment variable with the new location and restart your TeamCity.