Loading...

XML

Word

Printable

If you start standalone.bat, you can see:

-Xverbosegclog:"C:\j\workspace\wildfly-core\standalone\log\gc.log"

if you start standalone.ps1, you can see:

-Xlog:gc*:file=\"C:\j\workspace\wildfly-core\standalone\log\gc.log\":time,uptimemillis:filecount=5,filesize=3M

There is no reason why powershell script should behave differently than bat script in GC logging.

My understanding is that JDK with OpenJ9 should use verbosegclog, so first option is correct and powershell is wrong.

clones

JBEAP-31599 (8.1.z) WFCORE-7454 - GC log parameters are wrong on Semeru JDK on PowerShell scripts

is cloned by

JBEAP-31682 (8.0.z) WFCORE-7454 - GC log parameters are wrong on Semeru JDK on PowerShell scripts

is triggered by

JBEAP-31600 [8.2.0] GC log parameters are wrong on Semeru JDK on PowerShell scripts