[
https://issues.apache.org/jira/browse/DERBY-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575885#action_12575885
]
Daniel John Debrunner commented on DERBY-3466:
----------------------------------------------
> My first impression was that the 128-bit identifier kind of clutters the
> MBean view in JConsole (et. al.),
We shouldn't lose sight of the fact that Derby's MBeans are there to provide a
management and monitoring *api* for Derby through a standard mechanism (JMX).
Jconsole is just one way of providing a GUI to manipulate these MBeans and is
just a general purpose tool, so we shouldn't get too caught up on how they
appear in it.
Applications that using Derby are unlikely to show direct representations of
the MBeans, instead just making calls to their api attributes and operations.
Those applications do need a way of ensuring they are calling the MBean for the
correct Derby system, that's really what the system identifier is for,
especially in the future when it may be more typical to support multiple derby
instances in a jvm, with the possibility of some of those being "old 10.4"
versions.
> 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.
