System.gc() causes for jcl (BufferPoolMXBean)
Alan.Bateman at oracle.com
Fri Jun 19 08:10:44 UTC 2015
On 19/06/2015 07:00, Bernd Eckenfels wrote:
> Am Sat, 6 Jun 2015 19:07:07 +0200
> schrieb Bernd Eckenfels <ecki at zusammenkunft.net>:
>> - why is BufferPoolMXBean not tracking allocation failures, allocation
>> count, alignment flag and maximum size (maybe even modifyable).
>> Would it be worth to contribute something in this area or is that
>> supposed to be covered by some events (and if yes, when will they be
>> exposed to JMX).
When we created BufferPoolMXBean (in JSR-203) then the goal was to make
it easy to monitor current usage. It wouldn't be hard to track peak
usage if that is important. Direct buffers have not been page aligned
for some time so that is probably not worth trying to expose. The
nio-dev and serviceability-dev would be the right place to being
proposals in this area.
More information about the hotspot-gc-dev