Hi All is there any way to clean up the heap memor...
# general
p
Hi All is there any way to clean up the heap memory in wirmock docker container, I am running with JAVA_OPTS="-Xms512m -Xmx10g -XX:+UseG1GC -XX:InitiatingHeapOccupancyPercent=10 -XX:NewSize=2g -XX:MaxNewSize=2g -XX:ParallelGCThreads=8", it is not able to cleanup memory, within 3-4 mins of time all the memory gets exhausted and start getting OOM error
can some one let me know which GC algo would work over here?
l
This is more likely to do with things like the Wiremock request log than what GC algorithm to use. Are you running with options like
--no-request-journal
`--no-request-journal`: Disable the request journal, which records incoming requests for later verification. This allows WireMock to be run (and serve stubs) for long periods (without resetting) without exhausting the heap. The
--record-mappings
option isn’t available if this one is specified.
p
no I have not use that option "`--no-request-journal"`
let me try with that option, thanks a lot Lee for the advice
l
No worries. Definitely worth starting there. If you need the request journal then you can take a look at `--max-request-journal-entries`: Set maximum number of entries in request journal (if enabled). When this limit is reached oldest entries will be discarded.
p
Thank you Very much!! it sorted out the problem
l
Great news.