Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-6178

Clean shutdown of server with Artemis configured as backup logs warning

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 10.1.0.CR1, 10.1.0.Final
    • 10.0.0.Final
    • JMS
    • None

    Description

      In one of our failover tests there is logged error to server.log during clean shutdown of EAP 7.0.0.ER5 with Artemis configured as backup. (see attach config) This error is not expected and should not appear.

      Error log:

      12:18:19,509 ERROR [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=5d29fceb-cfd3-11e5-a0c8-11ddbbd9fb5b) AMQ224000: Failure in initialisation: java.lang.IllegalStateException: Container is down
	at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:716) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
	at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1]
	at org.wildfly.extension.messaging.activemq.jms.JMSService$3.activated(JMSService.java:154) [wildfly-messaging-activemq-7.0.0.ER5-redhat-1.jar:7.0.0.ER5-redhat-1]
	at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.callActivateCallbacks(ActiveMQServerImpl.java:1421) [artemis-server-1.1.0.redhat-7.jar:1.1.0.redhat-7]
	at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:1616) [artemis-server-1.1.0.redhat-7.jar:1.1.0.redhat-7]
	at org.apache.activemq.artemis.core.server.impl.SharedStoreBackupActivation.run(SharedStoreBackupActivation.java:85) [artemis-server-1.1.0.redhat-7.jar:1.1.0.redhat-7]
	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]

      Attachments

        Issue Links

          clones

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-3333 Clean shutdown of server with Artemis configured as backup logs warning

          • 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

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: WFLY

              People

                jmesnil1@redhat.com Jeff Mesnil
                jmesnil1@redhat.com Jeff Mesnil
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: