chennaji9 opened a new pull request, #11287:
URL: https://github.com/apache/rocketmq/pull/11287

   <!-- Please make sure the target branch is right. In most case, the target 
branch should be `develop`. -->
   
   ### Which Issue(s) This PR Fixes
   
   Fixes #11278
   
   ### Brief Description
   
   The broker JVM options in `docs/cn/Configuration_System.md` were 
syntactically invalid: every `-XX` option was missing the colon after `-XX` 
(e.g. `-XXMaxDirectMemorySize=15g`, `-XX+AlwaysPreTouch`), and the `-Xloggc` 
example had lost its colon and path separators (`-Xloggcdevshmmq_gc_%p.log`). 
Any option copied from the page fails with `Unrecognized option`.
   
   This PR fixes all 10 broken lines, aligning the Chinese page with the 
(already correct) `docs/en/Configuration_System.md` and 
`distribution/bin/runbroker.sh`:
   - `-XX:MaxDirectMemorySize=15g`, `-XX:+AlwaysPreTouch`, 
`-XX:-UseBiasedLocking`
   - `-XX:+UseG1GC -XX:G1HeapRegionSize=16m`, `-XX:G1ReservePercent=25`, 
`-XX:InitiatingHeapOccupancyPercent=30`
   - `-XX:+UseGCLogFileRotation`, `-XX:NumberOfGCLogFiles=5`, 
`-XX:GCLogFileSize=30m`
   - `-Xloggc:/dev/shm/mq_gc_%p.log`
   
   ### How Did You Test This Change?
   
   - Verified the broken forms are gone: `grep -n 
"XXMaxDirectMemorySize\|XX+Always\|Xloggcdev..." 
docs/cn/Configuration_System.md` returns no hits after the change.
   - Spot-checked the corrected options against a real JVM: `java 
-XX:+AlwaysPreTouch -XX:G1ReservePercent=25 -version` prints the version and 
exits 0 (before the fix the copied forms exit 1 with `Unrecognized option`).
   - No surrounding Chinese text was touched (`git diff` shows exactly the 10 
option lines, 10 insertions / 10 deletions).
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to