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 Tue, 19 Feb 2008 17:30:43 GMT

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

Daniel John Debrunner commented on DERBY-3429:

Another thought is that we need to see MBeans as the mechanism to manage Derby, not just an
api into existing management. Thus any application MBeans that are presenting a simplified/application
specific view of Derby's management should be using Derby's MBeans to manage Derby. This requires
that Derby's MBeans be available.

> 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