Uploaded image for project: 'AMQ Interconnect'
  1. AMQ Interconnect
  2. ENTMQIC-1949

Console continues to send traffic to the router when the broker is shutdown

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 1.0.0.GA
    • Router Console
    • None
    • Hide
      • Add the required http listener to the default qdrouterd config in etc/qpid-dispatch
        [rkieley@ic1rh qpid-dispatch]$ diff qdrouterd.conf.orig qdrouterd.conf
        34a35,42
        > listener {
        >     host: 192.168.2.208
        >     port: 5673
        >     authenticatePeer: no
        >     saslMechanisms: ANONYMOUS
        >     http: yes
        > }
        > 
        [rkieley@ic1rh qpid-dispatch]$ 
        
      • Create and start a default AMQ 7.0.1 broker instance
        • admin/admin/anonymous Y
        • Wait for the console to be available
      • Start a router with the updated config file in /etc/qpid-dispatch with PN_TRACE_FRM=1
        [rkieley@ic1rh ~]$ PN_TRACE_FRM=1 /usr/sbin/qdrouterd -c /etc/qpid-dispatch/qdrouterd.conf
        
      • Open the AMQ web console at http://localhost:8161/hawtio/login
      • login
      • Connect to the 'Dispatch Router'

      Variant A:

      • From another terminal execute '/.bin/artemis stop'
        • The 'Dispatch Router' 'tab' continues to be active and send traffic to the router although other tabs are no longer activate upon clicking
      • Restart the broker with './bin/artemis run'
        • Once the browser resets to the login page the traffic to the router stops

      Variant B:

      • If the broker is started with '--allow-kill' and you do a ./bin/artemis kill the traffic to the router also continues
        • Once the browser resets to the login page the traffic to the router does not stop - see attached screenshot.
      Show
      Add the required http listener to the default qdrouterd config in etc/qpid-dispatch [rkieley@ic1rh qpid-dispatch]$ diff qdrouterd.conf.orig qdrouterd.conf 34a35,42 > listener { > host: 192.168.2.208 > port: 5673 > authenticatePeer: no > saslMechanisms: ANONYMOUS > http: yes > } > [rkieley@ic1rh qpid-dispatch]$ Create and start a default AMQ 7.0.1 broker instance admin/admin/anonymous Y Wait for the console to be available Start a router with the updated config file in /etc/qpid-dispatch with PN_TRACE_FRM=1 [rkieley@ic1rh ~]$ PN_TRACE_FRM=1 /usr/sbin/qdrouterd -c /etc/qpid-dispatch/qdrouterd.conf Open the AMQ web console at http://localhost:8161/hawtio/login login Connect to the 'Dispatch Router' Variant A: From another terminal execute '/.bin/artemis stop' The 'Dispatch Router' 'tab' continues to be active and send traffic to the router although other tabs are no longer activate upon clicking Restart the broker with './bin/artemis run' Once the browser resets to the login page the traffic to the router stops Variant B: If the broker is started with '--allow-kill' and you do a ./bin/artemis kill the traffic to the router also continues Once the browser resets to the login page the traffic to the router does not stop - see attached screenshot.

      After using the broker provided 'Dispatch Router' interface to connect to the console, and stopping the broker, the console continues to send traffic to the router.

              eallen@redhat.com Ernest Allen (Inactive)
              rhn-support-rkieley Roderick Kieley
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: