FUSE Message Broker
  1. FUSE Message Broker
  2. MB-590

There's no way to monitor a slave broker in a shared filesystem master/slave setup via JMX

    Details

    • Type: Enhancement Enhancement
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: 5.2.0.2-fuse, 5.3.0.4-fuse
    • Component/s: None
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      When you set up a shared filesystem master and slave(s) you can manage the master instance via JMX or activemq-admin, however all of the slaves block on acquiring the database lock before starting up the JMX management context, which means you cannot attach jconsole to a slave or run any activemq-admin commands against it.

        Issue Links

          Activity

          Hide
          Dejan Bosanac
          added a comment -

          The fix is merged in the 5.3.0.x branch

          The slave broker can now be stopped with

          bin/activemq-admin stop --jmxurl service:jmx:rmi:///jndi/rmi://localhost:55564/jmxrmi

          Please also consult the comment in the original https://issues.apache.org/activemq/browse/AMQ-2306 issue

          Show
          Dejan Bosanac
          added a comment - The fix is merged in the 5.3.0.x branch The slave broker can now be stopped with bin/activemq-admin stop --jmxurl service:jmx:rmi: ///jndi/rmi://localhost:55564/jmxrmi Please also consult the comment in the original https://issues.apache.org/activemq/browse/AMQ-2306 issue
          Hide
          Matt Hernon
          added a comment -

          Dejan,

          Can you update the 'fixed version' for this issue. It's only 5.3.x, correct?

          Thanks,
          Matt

          Show
          Matt Hernon
          added a comment - Dejan, Can you update the 'fixed version' for this issue. It's only 5.3.x, correct? Thanks, Matt
          Hide
          Dejan Bosanac
          added a comment -

          Hi Matt,

          updated the issue with correct 'fix versions'. It's going into 5.3.0.6 and 5.3.0-psc-01-00RC1

          Regards,
          Dejan

          Show
          Dejan Bosanac
          added a comment - Hi Matt, updated the issue with correct 'fix versions'. It's going into 5.3.0.6 and 5.3.0-psc-01-00RC1 Regards, Dejan
          Hide
          Gary Tully
          added a comment -

          link to release generation issue.

          Show
          Gary Tully
          added a comment - link to release generation issue.

            People

            • Assignee:
              Dejan Bosanac
              Reporter:
              Stan Lewis
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: