Re: Monitoring of "Free RAM" returns invalid values
This might be an overflow. The management tree's highest numbers are java.lang.Integer (kind of history). If a value > Integer.MAX_VALUE is transferred, it turns negative. This needs to be solved in future.
Maybe this happens because the GC timer is triggered. I am monitoring for "Free RAM" but triggering the GC on used RAM, this is probably not optimal and maybe even too early, but we had the occasional memory leak in the past so I am commited to checking memory consumption in some way.