db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag.Wan...@Sun.COM (Dag H. Wanvik)
Subject Re: [jira] Commented: (DERBY-1387) Add JMX extensions to Derby
Date Fri, 28 Sep 2007 00:59:02 GMT
"Bernt M. Johnsen (JIRA)" <jira@apache.org> writes:

>     [ https://issues.apache.org/jira/browse/DERBY-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530654
] 
>
> Bernt M. Johnsen commented on DERBY-1387:
> -----------------------------------------
>
> On second thought. 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. Any comments?

>From your argument it makes sense to introduce this property, but
should the default be "off", though? I thought your argument was to
enable it for usability reasons, or did you decide against it for
security reasons?

Dag

Mime
View raw message