-
Bug
-
Resolution: Done
-
Blocker
-
None
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.
- is cloned by
-
JBEAP-31600 [8.2.0] GC log parameters are wrong on Semeru JDK on PowerShell scripts
-
- New
-
-
JBEAP-31682 (8.0.z) WFCORE-7454 - GC log parameters are wrong on Semeru JDK on PowerShell scripts
-
- Resolved
-
-
WFCORE-7454 GC log parameters are wrong on Semeru JDK on PowerShell scripts
-
- Resolved
-
- is incorporated by
-
JBEAP-31543 [GSS](8.1.z) Upgrade WildFly Core from 27.1.3.Final-redhat-00001 to 27.1.4.Final-redhat-00001
-
- Resolved
-