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

[AMQ7, broker shutdown, JMX connector] JVM does not exit if "connector" configured in management-context

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • AMQ 7.2.2.GA
    • AMQ 7.2.0.GA
    • None
    • None
    • Release Notes
    • Hide
      In previous releases, sometimes the broker did not properly close the management context when stopping the broker. The broker would appear to be stopped, but the JVM process never fully exited. Now there are checks to ensure that the management context is always closed when stopping the broker and the JVM process exits, even when a management context connector is configured.
      Show
      In previous releases, sometimes the broker did not properly close the management context when stopping the broker. The broker would appear to be stopped, but the JVM process never fully exited. Now there are checks to ensure that the management context is always closed when stopping the broker and the JVM process exits, even when a management context connector is configured.
    • Documented as Resolved Issue
    • Hide

      Needs Fixes from ENTMQBR-1831 to be in place for following steps :

      • configure the connector in the management.xml
      <management-context xmlns="http://activemq.org/schema">
   <connector connector-port="1099" connector-host="0.0.0.0"/>
   ....
      • start broker
      • get an address paging
      • simulate an issue accessing the disk paging directory.
      • the broker will stop but the JVM will not exit
      Show
      Needs Fixes from ENTMQBR-1831 to be in place for following steps : configure the connector in the management.xml <management-context xmlns= "http: //activemq.org/schema" > <connector connector-port= "1099" connector-host= "0.0.0.0" /> .... start broker get an address paging simulate an issue accessing the disk paging directory. the broker will stop but the JVM will not exit
    • AMQ Broker 1839

      If the connector is configured (below) and org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl#stop(boolean, boolean, boolean) is called (eg. due to criticalIOErrors) the JVM will not exit. 

      <management-context xmlns="http://activemq.org/schema">
   <connector connector-port="1099" connector-host="0.0.0.0"/>

        1. jstack-backup_3.log
          9 kB

              rhn-support-jbertram Justin Bertram
              rhn-support-pfox Patrick Fox (Inactive)
              Michal Toth Michal Toth
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: