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

Increased time gap in failover with MQ 7.5 client runtime

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Major
    • None
    • AMQ 7.5.0.GA
    • None
    • None
    • Hide

      Start a master slave pair of brokers (config attached) on one or two separate machines

      Once both brokers are up and running run junit test from test case

      mvn -Dtest=test_three test

      Once test is running do

      kill -SIGSTOP pid_master_broker

      Wait for slave broker to become active and look for two message in its log file:

      2019-11-12 13:10:54,639 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at 0.0.0.0:61616 for protocols [CORE,AMQP]
2019-11-12 13:11:16,763 DEBUG [org.apache.activemq.artemis.core.server.impl.ServerSessionImpl] Session with user=artemis, connection=RemotingConnectionImpl [ID=e08c25d6, clientID=null, nodeID=330f90bf-054d-11ea-9e77-7824af88f158, transportConnection=org.apache.activemq.artemis.core.remoting.impl.netty.NettyServerConnection@763fbc33[ID=e08c25d6, local= /192.168.1.106:61616, remote=/192.168.1.100:61072]] created a consumer on queue com_ig_trade_v0_order_dma/orderserver, filter = null

      the difference in time stamp shows the difference

      Show
      Start a master slave pair of brokers (config attached) on one or two separate machines Once both brokers are up and running run junit test from test case mvn -Dtest=test_three test Once test is running do kill -SIGSTOP pid_master_broker Wait for slave broker to become active and look for two message in its log file: 2019-11-12 13:10:54,639 INFO [org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at 0.0.0.0:61616 for protocols [CORE,AMQP] 2019-11-12 13:11:16,763 DEBUG [org.apache.activemq.artemis.core.server.impl.ServerSessionImpl] Session with user=artemis, connection=RemotingConnectionImpl [ID=e08c25d6, clientID=null, nodeID=330f90bf-054d-11ea-9e77-7824af88f158, transportConnection=org.apache.activemq.artemis.core.remoting.impl.netty.NettyServerConnection@763fbc33[ID=e08c25d6, local= /192.168.1.106:61616, remote=/192.168.1.100:61072]] created a consumer on queue com_ig_trade_v0_order_dma/orderserver, filter = null the difference in time stamp shows the difference

    Description

      There seems to be a difference in time it takes for a client to reconnect to a slave broker after it becomes active.
      With AMQ 2.6 client runtime it takes about 2 seconds

      2019-11-12 13:19:36,551 INFO  [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
2019-11-12 13:19:36,567 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at 0.0.0.0:5673 for protocols [AMQP]
2019-11-12 13:19:36,570 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at 0.0.0.0:61616 for protocols [CORE,AMQP]
2019-11-12 13:19:38,192 DEBUG [org.apache.activemq.artemis.core.server.impl.ServerSessionImpl] Session with user=artemis, connection=RemotingConnectionImpl [ID=36e4181c, clientID=null, nodeID=8ff4bb68-054e-11ea-9b9b-7824af88f158, transportConnection=org.apache.activemq.artemis.core.remoting.impl.netty.NettyServerConnection@da3b082[ID=36e4181c, local= /192.168.1.106:61616, remote=/192.168.1.100:62680]] created a consumer on queue com_ig_trade_v0_order_dma/orderserver, filter = null
2019-11-12 13:19:38,192 DEBUG [org.apache.activemq.artemis.core.server.impl.ServerSessionImpl] Session with user=artemis, connection=RemotingConnectionImpl [ID=7299684d, clientID=null, nodeID=8ff4bb68-054e-11ea-9b9b-7824af88f158, transportConnection=org.apache.activemq.artemis.core.remoting.impl.netty.NettyServerConnection@1218c801[ID=7299684d, local= /192.168.1.106:61616, remote=/192.168.1.100:62681]] created a consumer on queue com_ig_trade_v0_order_dma/orderserver, filter = null

      with AMQ 2.9 runtime client it takes about 20 seconds

      2019-11-12 13:10:54,492 INFO  [org.apache.activemq.artemis.core.server] AMQ224076: Undeploying address activemq.notifications
2019-11-12 13:10:54,607 INFO  [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
2019-11-12 13:10:54,634 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at 0.0.0.0:5673 for protocols [AMQP]
2019-11-12 13:10:54,639 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started EPOLL Acceptor at 0.0.0.0:61616 for protocols [CORE,AMQP]
2019-11-12 13:11:16,763 DEBUG [org.apache.activemq.artemis.core.server.impl.ServerSessionImpl] Session with user=artemis, connection=RemotingConnectionImpl [ID=e08c25d6, clientID=null, nodeID=330f90bf-054d-11ea-9e77-7824af88f158, transportConnection=org.apache.activemq.artemis.core.remoting.impl.netty.NettyServerConnection@763fbc33[ID=e08c25d6, local= /192.168.1.106:61616, remote=/192.168.1.100:61072]] created a consumer on queue com_ig_trade_v0_order_dma/orderserver, filter = null

      In both cases the same AMQ 7.5 broker is used.

      Client runtimes used
      2.6.3.redhat-00013
      2.9.0.redhat-00005

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2720 Connection Timeout now blocks on the retry, it should be asynchronous

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              rh-ee-ataylor Andy Taylor
              rhn-support-toross Tom Ross
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: