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-3429) Remove system property derby.system.jmx
Date Mon, 18 Feb 2008 18:36:36 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569982#action_12569982

Daniel John Debrunner commented on DERBY-3429:

If an application is using a security manager then it provides a much more flexible mechanism
to control which of Derby's MBeans are visible than the all or nothing approach of derby.system.jmx.
   An application using an embedded Derby with its own policy file can:
         - disable Derby from registering any MBeans
         - allow Derby to only register specific MBeans
         - allow authenticated JMX users to only perform specific actions on Derby's MBeans.

Having Derby always attempt to register its MBeans (as if derby.system.jmx=true) i think provides
a much more flexible environment, an application can provide limited or no management of Derby
directly but also support a "drill-down" for more sophisticated users.

The functionality being added in DERBY-3424 also allows the application to control the visibility
of Derby's MBeans in a dynamic manner rather than the static manner of derby.system.jmx. 

> Remove system property derby.system.jmx
> ---------------------------------------
>                 Key: DERBY-3429
>                 URL: https://issues.apache.org/jira/browse/DERBY-3429
>             Project: Derby
>          Issue Type: Sub-task
>            Reporter: Daniel John Debrunner
>            Priority: Minor
> I don't believe that derby.system.jmx provides any benefit and is counter to the concept
of using JMX for management.
> The one use case for it from DERBY-1387 is:
> Making the Derby JMX automatically available in the MBean server will make it impossible
for the user to make some application with an embedded Derby db manageable thorugh JMX without
also making Derby manageable thorugh JMX. I would think that this "all or nothing" granularity
could be a problem for some applications. So we would need an explicit derby.system.jmx property
for enabling the management service anyway.
> The functional spec contains no information as to why this is a useful feature.
> I wanted to separate out the discussion from the wider issues in DERBY-1387

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message