standalone.sh version commands use standalone.conf JAVA_OPTS and can move and delete in use GC logs

Environment

• JBoss Enterprise Application Platform (EAP)
  • 7.x
  • 8.x

Issue

• Upon running a version command likestandalone.sh -v, standalone.sh -V, or standalone.sh --version, GC logs were modified, moved to backupgc.log or deleted

Resolution

• Await improvement in a later EAP 8 update and avoid checking version info through standalone.sh in the meantime. This can be checked instead through other options mentioned in How to check the JBoss EAP 6/7/8 version?

Root Cause

• standalone.sh can enable GC logs automatically and back up existing GC logs from this when starting JBoss. These options and back up calls along with all other standalone.conf provided JAVA_OPTS also apply to standalone.sh when running a version command. So this can lead to unwanted modifications of the GC.log or the version command running with other unneeded options like a large max heap needed only for the JBoss server instance.
• Content from redhat.atlassian.net is not included.WFCORE-7576
• Content from redhat.atlassian.net is not included.JBEAP-32965

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.