If you start standalone.bat, you can see:
-Xverbosegclog:"C:\j\workspace\eap-8.x-scrip---453f8c18\22891958\test\jboss-eap-8.1\standalone\log\gc.log"
if you start standalone.ps1, you can see:
-Xlog:gc*:file=\"C:\j\workspace\eap-8.x-scrip---4025b2a8\9ce5147c\test\jboss-eap-8.1\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
-
- Resolved
-
- is triggering
-
-
- Resolved
-
