tomcat, zapcat, jmxremote...

[sa22]

Hi All!
Today i've set up zapcat for our productive tomcat's
zapcat show that all 3 our instances of tomcat has the same problem:

memory pool ps old gen fully committed on instance1
memory pool ps perm gen fully committed on instance1

memory pool ps old gen fully committed on instance2
memory pool ps perm gen fully committed on instance2

memory pool ps old gen fully committed on instance3
memory pool ps perm gen fully committed on instance3

What does it mean? How can I fix this?

[eskytthe]

Hi
Not sure, but try to take a look at the notes from the creator of zapcat: http://www.kjkoster.org/zapcat/Zabbi..._Template.html
(jump over zapcat configuration part in the start)
Hope it will help you.
BR
Erik

[sa22]

Are you talking about heap monitoring?
It seams nothing strange there:

[sa22]

this is our memory-related settings in tomcat:

It seams, after I've changed initial pool size from 1024 to 512 memory pool ps old gen fully committed warning has gone.

[sa22]

Yes, it seams the problem was in this memory settings. After some changes, all warnings has disappeared.

[Wescott569]

I will even go so far as to say that all serious Java applications today are written with the use of such application frameworks. From a monitoring perspective this is a great development.