[
https://issues.apache.org/jira/browse/DERBY-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner updated DERBY-3466:
-----------------------------------------
Attachment: d3466_mbean_system_id.txt
Patch that adds a runtime system identifier to the ObjectName Derby uses to
register MBeans in the form of the key property system.
ManagementMBean gains a getSystemIdentifier method which allows the application
registered MBean to obtain the system identifier for the system it is
monitoring.
The tests are enhanced to have a utility method that returns a valid ObjectName
for the system under test given a set of key properties.
javadoc expanded to explain the system identifier.
> Investigate ability to run multiple Derby systems in same JVM with different
> sets of MBeans.
> --------------------------------------------------------------------------------------------
>
> Key: DERBY-3466
> URL: https://issues.apache.org/jira/browse/DERBY-3466
> Project: Derby
> Issue Type: Sub-task
> Components: JMX
> Reporter: Daniel John Debrunner
> Priority: Minor
> Attachments: d3466_mbean_system_id.txt
>
>
> One of the reasons for JMX was to move away from system properties
> (specifically derby.system.home) to allow multiple Derby systems running
> within the same virtual machine. It would be good to get some unique
> naming/attribute scheme in the ObjectNames up front rather than only have it
> in some later version.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
