[
https://issues.apache.org/jira/browse/DERBY-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576119#action_12576119
]
John H. Embretsen commented on DERBY-3466:
------------------------------------------
I agree we should not put too much effort into how the presentation of Derby's
MBeans will look in generic tools without an additional abstraction layer,
although I'm sure a large portion of Derby's JMX users will access the beans
directly this way, at least to begin with.
One more question:
Other than by accessing Derby's MBeans, how can a user determine the value of
the system identifier? Is it being exposed by some other public API as well?
> 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
> Fix For: 10.4.0.0
>
> 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.
