Tomcat and Java Versions by MagicINFO Server Build

MagicINFO Server runs on Apache Tomcat and a Java runtime that the installer puts on the server. Security audits and vulnerability scanners usually ask which versions those are. This page lists what each generation of MagicINFO ships with, and shows how to read the versions on your own server, which is the answer that counts.

Versions by build

MagicINFO Server build	Tomcat	Java runtime
v4005 and earlier	7.0.65	Oracle JRE 7 Update 13
v4100 to v6002	8.0.43	Oracle JRE 8 Update 131
v7000 and later (V7, V8)	Tomcat 8	Zulu OpenJDK 8 Update 222
21.1000.3 (first MagicINFO 9 release, April 2021)	Tomcat 9 for new installations	Zulu OpenJDK 8 Update 282
21.1030	9.0.26	not stated in the release notes
21.1052.0 (hotfix, May 2025)	9.0.102	not stated in the release notes
21.1060.0 to 21.1091.1	9.0.105	Zulu OpenJDK 8 (seen on 21.1070)
21.1092.3 (July 2026)	9.0.115	not stated in the release notes

Notes on the table:

• Java before V7. Up to v6002 the installer only installed its own JRE when the computer had none; if Java was already present, MagicINFO used that one. From v7000 the bundled runtime is always used, whatever else is installed, and it is Zulu OpenJDK rather than Oracle Java.
• Tomcat 9 arrived with MagicINFO 9, but the 21.1000.3 release notes mention it for new installations. A server that was upgraded from V8 is worth checking: it may still run Tomcat 8.
• The MagicINFO 9 rows come from Samsung's release notes and from installations we have checked ourselves. The release notes do not mention every Java update after 21.1000.3, so confirm the Java version on your server with the steps below.
• Builds 21.1052.0 and 21.1060.0 install a new Tomcat. Their release notes ask you to back up the Tomcat folder before upgrading and to apply your own Tomcat changes again afterwards. Expect the same from any build that updates Tomcat: settings you added to server.xml, such as your certificate or TLS versions, may need to be put back.

Check what your server runs

The default installation folder is C:\MagicInfo Premium. Adjust the paths if yours differs.

Tomcat

Open C:\MagicInfo Premium\tomcat\RELEASE-NOTES in a text editor. Near the top is a line such as Apache Tomcat Version 9.0.105.

Or ask Tomcat itself, using the bundled Java, in PowerShell:

& "C:\MagicInfo Premium\jre\bin\java.exe" -cp "C:\MagicInfo Premium\tomcat\lib\catalina.jar" org.apache.catalina.util.ServerInfo

The output shows the server version, build date and the Java version it runs on.

Java

MagicINFO's bundled runtime lives in the jre folder of the installation:

& "C:\MagicInfo Premium\jre\bin\java.exe" -version

The output names the runtime and its update level, for example openjdk version "1.8.0_282" and Zulu. The same folder may also hold a plain-text release file that states the version.

Check this bundled runtime, not java -version on its own: a separate Java installed on the computer is not the one MagicINFO uses.

MagicINFO build

To match your server to the table, read the build number as shown in Finding the MagicINFO version.

TLS versions

Older builds enable TLS 1.0, TLS 1.1 and TLS 1.2 on the HTTPS connector, and the stock connector in C:\MagicInfo Premium\tomcat\conf\server.xml lists TLSv1,TLSv1.1,TLSv1.2,SSLv2Hello. TLS 1.0 and 1.1 are outdated and any audit will flag them.

Set sslEnabledProtocols="TLSv1.2,TLSv1.3" on the HTTPS connector, or TLSv1.2 alone if HTTPS stops answering on an older build with an older Java runtime. The full procedure, including the certificate, is in Change the HTTPS (TLS) certificate. Restart the MagicINFO service afterwards and allow several minutes before the web console answers again.

Keeping Tomcat and Java current

The Tomcat and Java versions come with the MagicINFO build, and Samsung ships updates to them, along with its own security fixes, as new server builds. The way to stay patched is to keep the server on the latest build:

1. Read the release notes of the newest build, including the upgrade preconditions (for example the required PostgreSQL version).
2. Back up the database and the conf, runtime and tomcat folders.
3. Run the new installer, then put back your own server.xml changes if the build replaced Tomcat.

The upgrade steps are in Updating MagicINFO Server, and the current platform requirements are in System requirements.

Last checked: October 2026, against build 21.1092.3.