StoRM Backend v. 1.11.20

Released on 12.04.2021 with StoRM v. 1.11.20. centos7


This release requires and install Java 11.


  • [STOR-1357] - StoRM Backend and native libs should run with Java 11

Installation and configuration

If you’re upgrading, you can update and restart StoRM backend service as follow:

yum update storm-backend-server

The update will upgrade also the native libraries as a dependency.
After the successful upgrade, the service will be restarted and you should have both Java 1.8 and Java 11 installed, but Java 11 must be set as your default runtime. None of the latest StoRM Java components still need Java 1.8 so it can be safely removed as follows:

yum remove java-1.8.0-openjdk java-1.8.0-openjdk-headless

You shouldn’t see storm backend component within the involved dependencies.
If you cannot remove it, you can also set java 11 as default runtime JDK by running:

update-alternatives --config java

and select the proper Java 11 option.

Now, don’t forget to restart service:

systemctl restart storm-backend-server

In case you have any kind of questions or problems please contact us.

In case of a clean installation please read the System Administrator Guide.

Known issue [Updated on 30.04.2021]

After the update from StoRM v1.11.19 to StoRM v1.11.20, if JVM and database are not on the same timezone, the Backend’s communication with MariaDB could start failing with the following error:

Caused by: java.sql.SQLException: The server time zone value 'CEST' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the serverTimezone configuration property) to use a more specifc time zone value if you want to utilize time zone support.

This bug is tracked at STOR-1397.

The possible solutions to avoid this problem are:

  • downgrade StoRM Backend to v1.11.19 (recommended)
  • apply a workaround within MariaDB
  • install StoRM Backend v1.11.21 beta

Read more here

Read more at: