Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-3113

Remote JMX server on slave shuts down during failback

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • AMQ 7.4.2.GA
    • None
    • None
    • None
    • Release Notes
    • +
    • Hide
      Previously, when a slave broker in a master-slave pair failed back to the original master broker, the JMX sever on the slave broker did not restart and could no longer be used. As a result of this issue, you could not manage or control the slave broker via JMX. However, other management methods (for example, via Jolokia or HTTP) were unaffected. This issue is now resolved. When a slave broker fails back to the original master broker, the JMX server is restarted.
      Show
      Previously, when a slave broker in a master-slave pair failed back to the original master broker, the JMX sever on the slave broker did not restart and could no longer be used. As a result of this issue, you could not manage or control the slave broker via JMX. However, other management methods (for example, via Jolokia or HTTP) were unaffected. This issue is now resolved. When a slave broker fails back to the original master broker, the JMX server is restarted.
    • Documented as Resolved Issue
    • Verified in a release
    • Hide

      https://github.com/sjhiggs/activemq-artemis/tree/ENTMQBR-2932/examples/features/ha/replicated-failback

      mvn clean verify

      Observe result during test:

      querying JMX server: service:jmx:rmi:///jndi/rmi://localhost:1199/jmxrmi
jmx attempt failed: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: 
	java.net.ConnectException: Connection refused (Connection refused)]
TEST 3: server0Live: true :: server1Live: null
      Show
      https://github.com/sjhiggs/activemq-artemis/tree/ENTMQBR-2932/examples/features/ha/replicated-failback mvn clean verify Observe result during test: querying JMX server: service:jmx:rmi: ///jndi/rmi://localhost:1199/jmxrmi jmx attempt failed: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused (Connection refused)] TEST 3: server0Live: true :: server1Live: null

    Description

      After failback, the remote JMX endpoint on the slave server is no longer accessible.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2925 HA failback, intermittently, does not occur

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          clones

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2932 Remote JMX server on slave shuts down during failback

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              csuconic@redhat.com Clebert Suconic
              dbruscin Domenico Francesco Bruscino
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: