Application built in such a way that it consum memory and hence, it's exhaust all memory and results in crashing Java. Probably GC is not running when it reaches to its threshold. Is there a way I can call GC explicitly without affecting running application. I believe need to identify the memory consumption as well.
On Sun 23 Dec, 2018, 2:23 AM Olaf Kock <tom...@olafkock.de wrote: > > On 22.12.18 20:17, Dhaval Jaiswal wrote: > > System has allocated all mentioned RAM. > > > > I assume 13 would be fine. > > Adding to John's question, what I forgot earlier: Another rule of thumb > is to identify the *minimum* amount of memory that the application can > run with, then add a bit of headroom. Typically there's no need to go > with a humongous heap if garbage collection has a chance to free it all > up quickly. Memory in webappliations typically tends to be largely > short-lived, and (especially) the young generation GC is typically > extremely quick. You want it to rather run often (e.g. through an > imposed memory limit) than rarely (due to a too large heapspace). > > Olaf > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
