January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11605) Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain

by Srinivas ev (Jira)

[ https://issues.jboss.org/browse/WFLY-11605?page=com.atlassian.jira.plugin... ] Srinivas ev updated WFLY-11605: ------------------------------- Labels: https://developer.jboss.org/thread/279503 (was: https://developer.jboss.org/message/987533#987533) > Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain > --------------------------------------------------------------------------------------- > > Key: WFLY-11605 > URL: https://issues.jboss.org/browse/WFLY-11605 > Project: WildFly > Issue Type: Bug > Components: Clustering, JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: Jeff Mesnil > Priority: Blocker > Labels: https://developer.jboss.org/thread/279503 > Attachments: Project component log.txt, Wildfly error abrupt failback.txt > > > Scenario - Master, and Slave Running on 2 VM's. > Master Wildfly - <replication-master cluster-name="my-cluster" group-name="srini-queues-cluster-group" check-for-live-server="true"/> > Slave Wildfly - <replication-slave cluster-name="my-cluster" group-name="srini-queues-cluster-group" allow-failback="false" max-saved-replicated-journal-size="1"/> > PFB below 2 errors. > At this time Slave will start deploying Queues even when Master wildfly is not stopped completely. Both management consoles can be reached. > Ideally, the Master server(Wildfly) should completely stop for Slave to start the deployment of queues and start the replication. > 2019/01/16 19:56:21,118+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224044: error acknowledging message: java.lang.NullPointer > Exception > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.removeReferenceByID(ServerConsumerImpl.java:811) > 2019/01/16 19:56:21,121+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224016: Caught exception: ActiveMQIllegalStateException[er > rorType=ILLEGAL_STATE message=null] > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.individualAcknowledge(ServerConsumerImpl.java:772) > at org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.individualAcknowledge(ServerSessionImpl.java:739) > Detailed logs are attached. > At this stage, 1st component in my project pipeline has identified the slave as master now and stick with sending messages to it. Whereas the other components in the pipeline still consuming from Master(based on consumer count). > This caused the break-in message flow. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11605) Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-11605?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet commented on WFLY-11605: ------------------------------------------ Is it reproducible with WildFly 15 (since Artemis has been upgraded since) ? > Slave Artemis in Wildfly 10.1.0.Final is starting without Master Shutdown - Split brain > --------------------------------------------------------------------------------------- > > Key: WFLY-11605 > URL: https://issues.jboss.org/browse/WFLY-11605 > Project: WildFly > Issue Type: Bug > Components: Clustering, JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: Jeff Mesnil > Priority: Blocker > Labels: https://developer.jboss.org/message/987533#987533 > Attachments: Project component log.txt, Wildfly error abrupt failback.txt > > > Scenario - Master, and Slave Running on 2 VM's. > Master Wildfly - <replication-master cluster-name="my-cluster" group-name="srini-queues-cluster-group" check-for-live-server="true"/> > Slave Wildfly - <replication-slave cluster-name="my-cluster" group-name="srini-queues-cluster-group" allow-failback="false" max-saved-replicated-journal-size="1"/> > PFB below 2 errors. > At this time Slave will start deploying Queues even when Master wildfly is not stopped completely. Both management consoles can be reached. > Ideally, the Master server(Wildfly) should completely stop for Slave to start the deployment of queues and start the replication. > 2019/01/16 19:56:21,118+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224044: error acknowledging message: java.lang.NullPointer > Exception > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.removeReferenceByID(ServerConsumerImpl.java:811) > 2019/01/16 19:56:21,121+05:30 ERROR [org.apache.activemq.artemis.core.server] (default I/O-2) AMQ224016: Caught exception: ActiveMQIllegalStateException[er > rorType=ILLEGAL_STATE message=null] > at org.apache.activemq.artemis.core.server.impl.ServerConsumerImpl.individualAcknowledge(ServerConsumerImpl.java:772) > at org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.individualAcknowledge(ServerSessionImpl.java:739) > Detailed logs are attached. > At this stage, 1st component in my project pipeline has identified the slave as master now and stick with sending messages to it. Whereas the other components in the pipeline still consuming from Master(based on consumer count). > This caused the break-in message flow. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11619) HA Singleton will not stop the service or deployment after merge the cluster-view if the elected node rejected by FullGC or suspended

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created WFLY-11619: --------------------------------------- Summary: HA Singleton will not stop the service or deployment after merge the cluster-view if the elected node rejected by FullGC or suspended Key: WFLY-11619 URL: https://issues.jboss.org/browse/WFLY-11619 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 16.0.0.Beta1 Reporter: Wolf-Dieter Fink Assignee: Paul Ferraro If a 2 node cluster has a HA Singleton deployment (no matter whether it is a service or deployment) a merge after a split caused by FullGC will end in running two nodes as a Singleton provider. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4283) Web management console reports 500 error while domain host controller is in bootup

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFCORE-4283?page=com.atlassian.jira.plugi... ] Yeray Borges moved JBEAP-16266 to WFCORE-4283: ---------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-4283 (was: JBEAP-16266) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Management (was: Web Console) Affects Version/s: 8.0.0.Beta2 (was: 7.1.4.GA) > Web management console reports 500 error while domain host controller is in bootup > ---------------------------------------------------------------------------------- > > Key: WFCORE-4283 > URL: https://issues.jboss.org/browse/WFCORE-4283 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 8.0.0.Beta2 > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > Attachments: eap-console-500.png > > > In EAP 7.1 domain setup, web management console executes the op `:read-children-resources(child-type=host)` when it starts. A host controller triggers managed server instances startup sequentially (SERVER_STOPPED to SERVER_STARTING) which may take some very long time for host controller to finish boot process (when there are dozens of managed server instances). And in this case `:read-children-resources(child-type=host)` operation could fail with 500 error when using web management console on domain master node. Resulting in the web console becomes un-usable for long time. > The operation `:read-children-resources(child-type=host)` needs a fix to avoid 500 error. > The web management console should start up as soon as the domain controller (master node) is available. Hosts and servers in the topology view should show up as soon as they're available. > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11594) Upgrade MP Metrics to 1.1.3.Final

by Rostislav Svoboda (Jira)

[ https://issues.jboss.org/browse/WFLY-11594?page=com.atlassian.jira.plugin... ] Rostislav Svoboda updated WFLY-11594: ------------------------------------- Description: Upgrade MP Metrics to 1.1.3.Final Details about 1.1.3.Final scope and fixes - https://github.com/smallrye/smallrye-metrics/issues/40#issuecomment-45312... Tag: https://github.com/smallrye/smallrye-metrics/releases/tag/1.1.3 was: Upgrade MP Metrics to 1.1.3.Final Details about 1.1.3.Final scope and fixes - https://github.com/smallrye/smallrye-metrics/issues/40#issuecomment-45312... > Upgrade MP Metrics to 1.1.3.Final > --------------------------------- > > Key: WFLY-11594 > URL: https://issues.jboss.org/browse/WFLY-11594 > Project: WildFly > Issue Type: Component Upgrade > Components: MP Metrics > Reporter: Marek Kopecký > Assignee: Jeff Mesnil > Priority: Major > > Upgrade MP Metrics to 1.1.3.Final > Details about 1.1.3.Final scope and fixes - https://github.com/smallrye/smallrye-metrics/issues/40#issuecomment-45312... > Tag: https://github.com/smallrye/smallrye-metrics/releases/tag/1.1.3 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-568) Fix Scale Mesh Job

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-568: --------------------------------------------- Summary: Fix Scale Mesh Job Key: SWSQE-568 URL: https://issues.jboss.org/browse/SWSQE-568 Project: Kiali QE Issue Type: Bug Reporter: Guilherme Baufaker Rêgo Assignee: Michael Foley Scale Mesh has changed over time but the job didn't keep up with the changes -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-563) Organize Saturn Test Cases in Polarion

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-563?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-563: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Organize Saturn Test Cases in Polarion > -------------------------------------- > > Key: SWSQE-563 > URL: https://issues.jboss.org/browse/SWSQE-563 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Saturn Test Cases need to be updated in Polarion (Specifically the Graph Related) > https://docs.google.com/spreadsheets/d/13H1HzFtUB7N5jlXSN-zUEOXyEdSycy4Np... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11449) Upgrade JGroups to 4.0.16.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11449?page=com.atlassian.jira.plugin... ] Radoslav Husar reassigned WFLY-11449: ------------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) > Upgrade JGroups to 4.0.16.Final > ------------------------------- > > Key: WFLY-11449 > URL: https://issues.jboss.org/browse/WFLY-11449 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 15.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Major > Fix For: 16.0.0.Beta1 > > > Changelog: https://issues.jboss.org/projects/JGRP/versions/12339241 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11618) Unable to deploy jts quickstart

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-11618?page=com.atlassian.jira.plugin... ] Eduardo Martins moved JBEAP-16265 to WFLY-11618: ------------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11618 (was: JBEAP-16265) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Affects Version/s: 15.0.1.Final (was: 7.2.0.GA.CR4) > Unable to deploy jts quickstart > ------------------------------- > > Key: WFLY-11618 > URL: https://issues.jboss.org/browse/WFLY-11618 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 15.0.1.Final > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > Due to the line in _application-component-2/src/main/resources/META-INF/jboss-ejb3.xml_ file: > {noformat} > <iiop:ejb-name>InvoiceManagerEJBImpl</iiop:ejb-name> > {noformat} > instead of > {noformat} > <ejb-name>InvoiceManagerEJBImpl</ejb-name> > {noformat} > *jts* quickstart fails with the following error: > {noformat} > [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:2.0.0.Final:deploy (default-cli) on project jts-application-component-2: Failed to execute goal deploy: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"jts-application-component-2.jar\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"jts-application-component-2.jar\" > [ERROR] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0085: Exception while parsing jboss-ejb3.xml: /content/jts-application-component-2.jar/META-INF/jboss-ejb3.xml > [ERROR] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[31,9] > [ERROR] Message: Missing required element(s): EJB_NAME"}}}} > {noformat} > I suppose this commit (https://github.com/jbossas/eap-quickstarts/commit/1cb5b5e74c19076d2a5c6fb...) should be cherrypicked to the current quickstarts branch. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11449) Upgrade JGroups to 4.0.16.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11449?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-11449: ---------------------------------- Description: Changelog: https://issues.jboss.org/projects/JGRP/versions/12339241 > Upgrade JGroups to 4.0.16.Final > ------------------------------- > > Key: WFLY-11449 > URL: https://issues.jboss.org/browse/WFLY-11449 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 15.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Fix For: 16.0.0.Beta1 > > > Changelog: https://issues.jboss.org/projects/JGRP/versions/12339241 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2019