Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-27384

[QE](8.0.z) Artemis is logging warnings during clean shutdown of server in cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 8.0 Update 2
    • ActiveMQ
    • None
    • False
    • None
    • False
    • Hide 
      git clone -b master git@gitlab.cee.redhat.com:jbossqe-eap/messaging-testsuite.git
cd messaging-testsuite/scripts/

groovy DEAP_ZIP_URL=file://<local_path_to_zip_dir>/jboss-eap....zip PrepareServers7.groovy 
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap

cd ../jboss-hornetq-testsuite/ 
mvn clean install -B -Dartemis.version=2.21.0 -Deap7.org.jboss.qa.hornetq.apps.clients.version=8.1719212601-SNAPSHOT -DreuseForks=false -Dmaven.test.failure.ignore=true -Deap7.clients.version=8.1719212601-SNAPSHOT -Dsurefire.failIfNoSpecifiedTests=false -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true -Dtest=ClusterTestCase#testNoWarningErrorsDuringRestartingNodesInCluster | tee log
      Show
      git clone -b master git@gitlab.cee.redhat.com:jbossqe-eap/messaging-testsuite.git cd messaging-testsuite/scripts/ groovy DEAP_ZIP_URL=file: //<local_path_to_zip_dir>/jboss-eap....zip PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean install -B -Dartemis.version=2.21.0 -Deap7.org.jboss.qa.hornetq.apps.clients.version=8.1719212601-SNAPSHOT -DreuseForks= false -Dmaven.test.failure.ignore= true -Deap7.clients.version=8.1719212601-SNAPSHOT -Dsurefire.failIfNoSpecifiedTests= false -Dmaven.wagon.http.ssl.insecure= true -Dmaven.wagon.http.ssl.allowall= true -Dtest=ClusterTestCase#testNoWarningErrorsDuringRestartingNodesInCluster | tee log

      When shutting down the server in cluster, Artemis is sometimes logging warnings like:

      08:52:40,408 WARN [org.apache.activemq.artemis.core.server] (Thread-0 (ActiveMQ-remoting-threads-ActiveMQServerImpl::name=default-253785251)) AMQ222061: Client connection failed, clearing up resources for session be777421-352b-11ef-b9c6-fa163e1c44e0 
      08:52:40,423 WARN  [org.apache.activemq.artemis.core.server] (Thread-0 (ActiveMQ-remoting-threads-ActiveMQServerImpl::name=default-253785251)) AMQ222107: Cleared up resources for session be777421-352b-11ef-b9c6-fa163e1c44e0
      08:53:35,017 WARN  [org.apache.activemq.artemis.core.client] (activemq-discovery-group-thread-dg-group10 (DiscoveryGroup-249566635)) AMQ212034: There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node. nodeID=b581e773-352b-11ef-a698-fa163e1c44e0 
      08:53:47,302 WARN [org.apache.activemq.artemis.core.server] (Thread-16 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@36f38f2a)) AMQ224091: Bridge ClusterConnectionBridge@1fe7ab2b [name=$.artemis.internal.sf.my-cluster.b581e773-352b-11ef-a698-fa163e1c44e0, queue=QueueImpl[name=$.artemis.internal.sf.my-cluster.b581e773-352b-11ef-a698-fa163e1c44e0, postOffice=PostOfficeImpl [server=ActiveMQServerImpl::name=default], temp=false]@520221e3 targetConnector=ServerLocatorImpl (identity=(Cluster-connection-bridge::ClusterConnectionBridge@1fe7ab2b [name=$.artemis.internal.sf.my-cluster.b581e773-352b-11ef-a698-fa163e1c44e0, queue=QueueImpl[name=$.artemis.internal.sf.my-cluster.b581e773-352b-11ef-a698-fa163e1c44e0, postOffice=PostOfficeImpl [server=ActiveMQServerImpl::name=default], temp=false]@520221e3 targetConnector=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=9080&host=rhos-d-rhel8-large-146], discoveryGroupConfiguration=null]]::ClusterConnectionImpl@311557476[nodeUUID=ad9b812c-352b-11ef-bfaa-fa163e1c44e0, connector=TransportConfiguration(name=connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=8080&host=rhos-d-rhel8-large-146, address=jms, server=ActiveMQServerImpl::name=default])) [initialConnectors=[TransportConfiguration(name=connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=9080&host=rhos-d-rhel8-large-146], discoveryGroupConfiguration=null]] is unable to connect to destination. Retrying

       

      Expectation is that during clean shutdown no warnings/errors will be logged.

      Customer Impact: All warnings are harmless but restarting EAP server is normal admin operation and server should not log any warning/error. Log monitoring might cause false alarm on customer side.

        1. logs.zip
          8.56 MB

              Unassigned Unassigned
              gsamios Giorgos Samios
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: