Hi Brian,
Am 30.12.2023 um 21:42 schrieb Brian Braun:
I don't have any Java OOME exceptions, so it is not that my objects don't
fit. Even if I supply 300MB to the -Xmx parameter. In fact, as I wrote, I
don't think the Heap and non-heap usage is the problem. I have been
inspecting those and their usage seems to be normal/modest and steady. I
can see that using the Tomcat Manager as well as several other tools (New
Relic, VisualVM, etc).
Regarding the 1GB I am giving now to the -Xms parameter: I was giving just
a few hundreds and I already had the problem. Actually I think it is the
same if I give a few hundreds of MBs or 1GB, the JVM still starts using
more memory after 3-4 days of running until it takes 1.5GB. But during the
first 1-4 days it uses just a few hundred MBs.
So if this is not heap memory (-Xmx) it must be some other memory the
JVM uses.
I guess we can rule out reserved code cache (-XX:ReservedCodeCacheSize)
and stack size (-Xss) because they should have fixed sizes and you've
written earlier that you checked the number of threads.
This leaves us with meta space (-XX:MaxMetaspaceSize) and native/direct
memory (-XX:MaxDirectMemorySize). You can try to limit that or use the
Java flight recorder and tools like Mission Control or VisualVM to make
that kind of memory usage visible.
Regards,
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
