[ 
https://issues.apache.org/jira/browse/DERBY-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575700#action_12575700
 ] 

John H. Embretsen commented on DERBY-3466:
------------------------------------------

My first impression was that the 128-bit identifier kind of clutters the MBean 
view in JConsole (et. al.), and seems to provide little value as of yet. I'm 
afraid users will ask themselves what the purpose of this number is. However, I 
agree it can be useful if a solution for DERBY-1228 is provided*, and that 
adding such mandatory key properties to all object names later might be more 
problematic than doing it now.

Making it possible to set a custom identifier (e.g. "myDerbySystem2" instead of 
a default such as "c013800d-0118-8425-3abf-fffff03de2d0") as a property or 
something would provide users with an option to reduce the "clutter" somewhat, 
so I'm all for that.

*) 
So the system identifiers that are now part of all of Derby MBeans' ObjectNames 
are there in case DERBY-1228 ("Make it possible to run multiple instances of 
Derby within the same VM") is resolved? Or is it possible to run multiple Derby 
systems in the same JVM today?


> 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.

Reply via email to