db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3466) Investigate ability to run multiple Derby systems in same JVM with different sets of MBeans.
Date Tue, 26 Feb 2008 05:07:51 GMT

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

Daniel John Debrunner commented on DERBY-3466:
----------------------------------------------

A simple initial scheme could be to have a system attribute for each MBean registered by Derby.
The JMXManagamentService could automatically add this to the ObjectName when MBeans are registered
with it. Initially a newly created UUID could be used as the system identifier. I have some
code that does this, I'll submit a patch soon.

Future options could allow the application to provide a system identifier in derby.properties.


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


Mime
View raw message