Introduction to the Derby MBeans

Derby provides the MBeans described in this section.

The public API documentation for each Derby MBean describes its features in detail.


VersionMBean exposes version information about the running Derby system jar file.


JDBCMBean exposes information about the JDBC driver.


ManagementMBean manages the state of the Derby MBeans (registered or not).


NetworkServerMBean monitors and manages a running instance of the Network Server.


CacheManagerMBean monitors the page cache, the container cache, and the statement cache of a running database instance.

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: filter status: REJECTED

To loosen the restrictions, you must relax the default deserialization filter declared in $JAVA_HOME/conf/management/ Edit that file in the JVM of your JMX client. The following liberal deserialization filter will work with org.apache.derby.mbeans.CacheManagerMBean:*
Related reference
Enabling and disabling JMX
Using JConsole to access the Derby MBeans
Using custom Java code to access the Derby MBeans
Troubleshooting JMX connection issues