[jboss-jira] [JBoss JIRA] (WFLY-10562) Initialization of backup fails on Lifecycle context is no longer valid
Jeff Mesnil (JIRA)
issues at jboss.org
Thu Jun 14 10:38:01 EDT 2018
[ https://issues.jboss.org/browse/WFLY-10562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591601#comment-13591601 ]
Jeff Mesnil commented on WFLY-10562:
------------------------------------
[~swd847] this regression occurs because the service can be installed outside the scope of the start context.
In this use case, the Artemis server is started as a backup and put 'on hold'. None of the MSC service that uses Artemis resources are started as they have a dependency on this ActiveMQActivationService (maybe the term "barrier" would have been more appropriate).
When the Artemis becomes live (because its master has stopped and it failed over), we install the activation service which in turn install others Artemis-related service.
Would you be ok if I revert this one to install on the serviceContainer as before?
> Initialization of backup fails on Lifecycle context is no longer valid
> ----------------------------------------------------------------------
>
> Key: WFLY-10562
> URL: https://issues.jboss.org/browse/WFLY-10562
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Erich Duda
> Assignee: Jeff Mesnil
> Priority: Blocker
>
> *Scenario:*
> * There are two Wildfly servers configured as messaging live-backup pair
> * Live server is killed
> *Expectation:* Backup server will become active.
> *Reality:* Backup server doesn't become active because of failure in initialisation \[1\].
> *Users impact:* Messaging HA does not work.
> *Blocker priority* was chosen because this is regression against Wildfly 13 and breaks all messaging HA scenarios.
> I found out that the regression is caused by WFLY-10538.
> The issue can be reproduced in Wildfly version: 5e5ac8378d7780a2b4c614670e0dd88ca30470d5
> \[1\]
> {code}
> 19:59:17,028 ERROR [org.apache.activemq.artemis.core.server] (AMQ119000: Activation for server ActiveMQServerImpl::serverUUID=fde2ba47-6e7a-11e8-b92f-fa163e6eb24b) AMQ224000: Failure in initialisation: java.lang.IllegalStateException: Lifecycle context is no longer valid
> at org.jboss.msc.service.ServiceControllerImpl$StartContextImpl.getChildTarget(ServiceControllerImpl.java:2016) [jboss-msc-1.4.2.Final.jar:1.4.2.Final]
> at org.wildfly.extension.messaging.activemq.jms.JMSService$3.activated(JMSService.java:163) [wildfly-messaging-activemq-14.0.0.Beta1-SNAPSHOT.jar:14.0.0.Beta1-SNAPSHOT]
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.callActivateCallbacks(ActiveMQServerImpl.java:1897) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:2112) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.server.impl.SharedStoreBackupActivation.run(SharedStoreBackupActivation.java:90) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$ActivationThread.run(ActiveMQServerImpl.java:2514) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list