Skip to content

openjdk 11 - UseGCLogFileRotation not accepted in the JVM #196

@pier4r

Description

@pier4r

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 4.10
  • Ruby:
  • Distribution: CentOS 7.7
  • Module version: 3.2.0

How to reproduce (e.g Puppet code you use)

Use openjdk 11. Namely

class { 'java':
    package => 'java-11-openjdk',
}

...

class { 'confluence':
    version           => $confversion,
    installdir        => '/opt/atlassian',
    homedir           => '/data/confluence-home',
    javahome          => $facts['java_default_home'],
    jvm_xmx           => '10G',
    jvm_xms           => '2G',
    java_opts         => '-XX:MaxMetaspaceSize=512m -XX:+UseG1GC -Dconfluence.upgrade.recovery.file.enabled=false -Dsynchrony.proxy.healthcheck.disabled -Dsynchrony.memory.max=3G -Dsynchrony.enable.xhr.fallback=true -Datlassian.plugins.enable.wait=300',
    manage_server_xml => 'template',
    tomcat_proxy      => {
            scheme    => 'https',
            proxyName => 'localhost',
            proxyPort => '8009',
    },
}

What are you seeing

Puppet can run but confluence can't.

The problem that confluence notify is the following:

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/atlassian-confluence-7.1.1/logs/gc-2020-01-29_16-51-35.log instead.
Unrecognized VM option 'UseGCLogFileRotation'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

In: /opt/atlassian/atlassian-confluence-7.1.1/logs/catalina.out

What behaviour did you expect instead

That confluence could work.

Output log

Any additional information you'd like to impart

We used the module version 3.0.0 , there the log option is not reported.
In the version 3.2.0 there is, here: https://github.com/voxpupuli/puppet-confluence/blob/v3.2.0/templates/setenv.sh.erb#L85

My request is whether the module could have

  • either setenv.sh compatible with openjdk 11
  • or a setenv.sh that can be controlled with more granularity, so that one can override default decisions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions