Derby
  1. Derby
  2. DERBY-3424

Add an MBean that an application can register to change the state of Derby's JMX management

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.4.1.3
    • Component/s: JMX
    • Labels:
      None

      Description

      JMX in Derby was originally proposed as a mechanism to configure Derby replacing or enhancing the system properties which tend to be static in nature. Thus it is somewhat ironic that jmx is enabled with a static system property derby.system.jmx.

      I propose to add a public mbean that allows the state Derby's JMX management to be changed. This bean is not automatically registered by Derby if derby.system.jmx is false, but instead can be registered by an application. I believe this could occur at any time so that JMX could be enabled on a running application, possibly by a remote client.

      This standard Mbean (o.a.d.mbeans.Management & ManagementMBean) would have these operations & attribute:

      public boolean isManagementActive();
      public void startManagement();
      public void stopManagement();

      If Derby is not booted within the jvm then the operations would be no-ops.

      If derby.system.jmx is true then Derby will itself register an mbean that implements ManagementMBean to allow dynamic control of the visibility of Derby's mbeans.

        Issue Links

          Activity

          Daniel John Debrunner created issue -
          Daniel John Debrunner made changes -
          Field Original Value New Value
          Description JMX in Derby was originally proposed as a mechanism to configure Derby replacing or enhancing the system properties which tend to be static in nature. Thus it is somewhat ironic that jmx is enabled with a static system property derby.system.jmx.

          I propose to add a public mbean that allows the state Derby's JMX management to be changed. This bean is not automatically registered by Derby if derby.system.jmx is false, but instead can be registered by an application. I believe this could occur at any time so that JMX could be enabled on a running application, possibly by a remote client.

          This standard Mbean (o.a.d.jmx.Management & ManagementMBean) would have these operations & attribute:

              public boolean isManagementActive();
              public void startManagement();
              public void stopManagement();

          If Derby is not booted within the jvm then the operations would be no-ops.

          If derby.system.jmx is true then Derby will itself register an mbean that implements ManagementMBean to allow dynamic control of the visibility of Derby's mbeans.

          JMX in Derby was originally proposed as a mechanism to configure Derby replacing or enhancing the system properties which tend to be static in nature. Thus it is somewhat ironic that jmx is enabled with a static system property derby.system.jmx.

          I propose to add a public mbean that allows the state Derby's JMX management to be changed. This bean is not automatically registered by Derby if derby.system.jmx is false, but instead can be registered by an application. I believe this could occur at any time so that JMX could be enabled on a running application, possibly by a remote client.

          This standard Mbean (o.a.d.mbeans.Management & ManagementMBean) would have these operations & attribute:

              public boolean isManagementActive();
              public void startManagement();
              public void stopManagement();

          If Derby is not booted within the jvm then the operations would be no-ops.

          If derby.system.jmx is true then Derby will itself register an mbean that implements ManagementMBean to allow dynamic control of the visibility of Derby's mbeans.

          John H. Embretsen made changes -
          Link This issue is part of DERBY-1387 [ DERBY-1387 ]
          Daniel John Debrunner made changes -
          Component/s JMX [ 12312171 ]
          Dag H. Wanvik made changes -
          Issue Type New Feature [ 2 ] Improvement [ 4 ]
          Daniel John Debrunner made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Fix Version/s 10.4.1.3 [ 12313111 ]
          Resolution Fixed [ 1 ]
          Gavin made changes -
          Workflow jira [ 12423678 ] Default workflow, editable Closed status [ 12798520 ]

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development