• Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s:
    • Component/s: JMX
    • Labels:


      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

        Issue Links


          Daniel John Debrunner created issue -
          Daniel John Debrunner made changes -
          Field Original Value New Value
          Component/s JMX [ 12312171 ]
          Daniel John Debrunner made changes -
          Assignee Daniel John Debrunner [ djd ]
          Daniel John Debrunner made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          Fix Version/s [ 12312540 ]
          Kristian Waagan made changes -
          Link This issue is related to DERBY-3887 [ DERBY-3887 ]
          Gavin made changes -
          Workflow jira [ 12423827 ] Default workflow, editable Closed status [ 12798753 ]


            • Assignee:
              Daniel John Debrunner
              Daniel John Debrunner
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: