confluence-server 6.13.23-adoptopenjdk8

[Oriol Albareda]

Hello Atlassian team,

cause CVE-2021-26084 I need to upgrade to version 6.13.23, I'm currently working with 6.13.21-adoptopenjdk8 version, so I need to update to the mentioned version.

I've been checking on docker hub but I cannot find the 6.13.23-adoptopenjdk8:

https://hub.docker.com/r/atlassian/confluence-server/tags?page=1&ordering=last_updated&name=6.13.23

Is this version expected to be uploaded to docker hub?

Thank you in advance

[Daniel Eads]

Hi @Oriol Albareda ,

We've built the image for 6.13.23 - and while not explicitly tagged as such, it does use AdoptOpenJDK as the JRE. You can pull the image (with no tag) and it will be the same image as it would be with the -adoptopenjdk tag:

docker pull atlassian/confluence-server:6.13.23

Cheers,
Daniel | Atlassian Support

[Oriol Albareda]

Hi @Daniel Eads ,

after changing my deployment to the version you mentioned, the confluence-server is throwing fatal errors:

Using Java: /opt/java/openjdk/bin/java
2021-09-10 07:23:38,402 INFO [main] [atlassian.confluence.bootstrap.SynchronyProxyWatchdog] A Context element for ${confluence.context.path}/synchrony-proxy is found in /opt/atlassian/confluence/conf/server.xml. No further action is required
---------------------------------------------------------------------------
NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
[0.001s][warning][gc] -Xloggc is deprecated. Will use -Xlog:gc:/opt/atlassian/confluence/logs/gc-2021-09-10_07-23-38.log instead.
Unrecognized VM option 'UseGCLogFileRotation'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

There is some java parameters warnings about deprecation and a unrecognized parameter... This could be causing the fatal exception?

Thank you

[Earl McCutcheon]

Hello @Oriol Albareda ,

Looking at the error you are hitting:

Unrecognized VM option 'UseGCLogFileRotation'
 Error: Could not create the Java Virtual Machine.
 Error: A fatal exception has occurred. Program will exit.

Lines up with a Java issue described in the following KB article:

• https://confluence.atlassian.com/confkb/unrecognized-jvm-gc-options-when-using-java-11-1002472841.html

As covered in the KB:

In Java 11 some JVM flags including those used in Java 8 for Garbage Collection Logging have been removed.

If these are still contained in the JVM flags specified in the setenv.sh or setenv.bat the JVM will not be able to start.

and the KB goes into a bit more detail about the solution but provides the following fix:

Solution

Either add the following JVM option to the setenv.sh or setenv.bat file, or convert the GC options to the new Xlog format.

XX:+IgnoreUnrecognizedVMOptions

Please give this a go, and let us know if it solves the issue.

Regards,
Earl

[Oriol Albareda]

Hello @Earl McCutcheon,

I'm using this image from a Kubernetes cluster and I'm not sure on how to add this argument to be recognized by the deployment.

Should I add some tag to the environment variables table?

Thank you

[Alexis Robert]

Hi @Oriol Albareda , 

there is usually a little bit of dealy between releases being pushed to Docker, the same happened for example for 6.13.20 where the adoptopenjdk version was pushed 3 days after the vanilly version.

You might just need to wait a few days !

Let me know if this helps, 

--Alexis