CacheManagerMBean
CacheManagerMBean monitors the page cache, the
container cache, and the statement cache of a running database
instance.
- Interface:
org.apache.derby.mbeans.CacheManagerMBean
- Implementation:
org.apache.derby.impl.services.cache.ConcurrentCacheMBeanImpl
(not in the public API)
- ObjectName:
org.apache.derby:type=CacheManager,name=PageCache,db=<databaseDir>,system=<sysID>
(monitors the page cache), or
org.apache.derby:type=CacheManager,name=ContainerCache,db=<databaseDir>,system=<sysID>
(monitors the container cache), or
org.apache.derby:type=CacheManager,name=StatementCache,db=<databaseDir>,system=<sysID>
(monitors the statement cache)
- Instruments:
org.apache.derby.impl.services.cache.ConcurrentCache
For security reasons, JDK 20 restricted the deserialization of objects by remote MBeans. You will need to loosen those restrictions if you see the following message when accessing the org.apache.derby.mbeans.CacheManagerMBean:
java.io.InvalidClassException: filter status: REJECTED
To loosen the restrictions, you must relax the default deserialization filter declared in $JAVA_HOME/conf/management/management.properties. Edit that file in the JVM of your JMX client. The following liberal deserialization filter will work with org.apache.derby.mbeans.CacheManagerMBean:
com.sun.management.jmxremote.serial.filter.pattern=*