Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-1387 Add JMX extensions to Derby
  3. DERBY-3435

Add an MBean for monitoring and managing the Network Server


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


      Most functionality of and information about a running instance of the Network Server is currently only available from the host running the Network Server, using the NetworkServerControl API.

      With a JMX Management and Monitoring service in place utilizing JMX (DERBY-1387), it is possible to expose some of the Network Server functionality and information through an MBean that is specific to the Network Server, to both local and remote users (JMX clients), subject to security restrictions. Access to Derby libraries on the client side is not even a requirement, potentially making a server administrator's job a lot easier.


        1. d3435_v01.diff
          19 kB
          John H. Embretsen
        2. d3435_v01.stat
          0.3 kB
          John H. Embretsen
        3. derby-3435-live-data-v0.diff
          6 kB
          Bernt M. Johnsen
        4. derby-3435-live-data-v0.stat
          0.4 kB
          Bernt M. Johnsen
        5. derby-3435-live-data-v1.zip
          2 kB
          Bernt M. Johnsen
        6. derby-3435-live-data-v2.zip
          2 kB
          Bernt M. Johnsen
        7. derby-3435-live-data-fix-v0.zip
          1 kB
          Bernt M. Johnsen
        8. derby-3435-live-data-fix2-v0.diff
          3 kB
          Bernt M. Johnsen
        9. d3435_NetworkServerMBeanTest_v01.diff
          16 kB
          John H. Embretsen
        10. d3435_javadocUpdates.diff
          29 kB
          John H. Embretsen



            • Assignee:
              johnemb John H. Embretsen
              johnemb John H. Embretsen
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: