July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10474) AMQ119012: Timed out waiting to receive initial broadcast from cluster

by Erich Duda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10474?page=com.atlassian.jira.plugin... ] Erich Duda commented on WFLY-10474: ----------------------------------- [~jmesnil] This issue is blocker for Wildfly 14. Can you please take a look. It looks like bug in JGroups. > AMQ119012: Timed out waiting to receive initial broadcast from cluster > ---------------------------------------------------------------------- > > Key: WFLY-10474 > URL: https://issues.jboss.org/browse/WFLY-10474 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 13.0.0.Beta1 > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Critical > Labels: blocker-WF14 > > In messaging HA scenarios we see that tests sometimes fail because of exception \[1\]. The exception is thrown from {{ServerLocatorImpl::createSessionFactory}} which waits until initial broadcast from cluster is received, but it is not received in 10 seconds timeout. In following scenario the issue causes split brain - both live and backup are active at the same time. > *Scenario* > * There are two Wildfly/Artemis servers configured as Live-Backup pair > * Live server is killed > * Backup server becomes new Live server > * Live server is restarted and failback is performed > *Expectation:* Failback performs successfully. Original Live becomes Live again and original Backup becomes Backup again. > *Reality:* After the Live is restarted, it does not detect that there is already another active Live with the same nodeId and it activates (becomes Live) so both Live and Backup are active at the same time. > *Technical details* > I found out that original Live server does not detect that its Backup is active, because SharedNothingLiveActivation::isNodeIdUsed returns false. I added more logs to this method and found out that the {{false}} is returned from line \[2\] after that the exception \[1\] is thrown. > *Investigation report* > I tried to downgrade Artemis to {{1.5.5.jbossorg-010}} version but I hit the same issue. So the issue is not caused by recent Artemis upgrade. > It is regression against EAP 7.1.0.GA but it is not regression against Wildfly 12. > We see the issue only with JGroups. I tried to run the test with Netty discovery and it passed 50 times in row. > \[1\] > {code} > ActiveMQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=AMQ119012: Timed out waiting to receive initial broadcast from cluster] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:749) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:627) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connectNoWarnings(ServerLocatorImpl.java:633) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation.isNodeIdUsed(SharedNothingLiveActivation.java:280) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation.run(SharedNothingLiveActivation.java:90) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:539) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:485) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:413) [artemis-jms-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:205) [wildfly-messaging-activemq-13.0.0.Beta2-SNAPSHOT.jar:13.0.0.Beta2-SNAPSHOT] > at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:64) [wildfly-messaging-activemq-13.0.0.Beta2-SNAPSHOT.jar:13.0.0.Beta2-SNAPSHOT] > at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:99) [wildfly-messaging-activemq-13.0.0.Beta2-SNAPSHOT.jar:13.0.0.Beta2-SNAPSHOT] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_171] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_171] > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.2.Final.jar:2.3.2.Final] > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [jboss-threads-2.3.2.Final.jar:2.3.2.Final] > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [jboss-threads-2.3.2.Final.jar:2.3.2.Final] > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [jboss-threads-2.3.2.Final.jar:2.3.2.Final] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171] > at org.jboss.threads.JBossThread.run(JBossThread.java:485) [jboss-threads-2.3.2.Final.jar:2.3.2.Final] > {code} > \[2\] https://github.com/rh-messaging/jboss-activemq-artemis/blob/465eb8733e465... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-337) Multi Namespace Test Mesh Traffice Generator Failure

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-337?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo closed SWSQE-337. ----------------------------------------- Resolution: Out of Date > Multi Namespace Test Mesh Traffice Generator Failure > ---------------------------------------------------- > > Key: SWSQE-337 > URL: https://issues.jboss.org/browse/SWSQE-337 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Minor > > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-Test-Meshe... > TASK [Deploy Traffic Generator ConfigMaps to Kiali Namespaces] ***************** > fatal: [localhost]: FAILED! => {"msg": "'kiali_test_hourglass_route' is undefined"} > to retry, use: --limit @/home/jenkins/workspace/Kiali-Test-Meshes-Ansible/checkout-directory/test-service/deploy/ansible/deploy_test_multiple_namespaces_meshes.retry -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2707) CSS for test results panel/dock design

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2707?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2707: ------------------------------------- [~danielezonca] Thanks, good to know. And it sounds like the data points for the test as a whole (Overall results, Completed timestamp, # of scenarios run...) will be available thought the JUnit test results as well. > CSS for test results panel/dock design > -------------------------------------- > > Key: DROOLS-2707 > URL: https://issues.jboss.org/browse/DROOLS-2707 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Sarah Rambacher > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-07-05 at 11.33.41 AM.png, Screen Shot 2018-07-11 at 3.03.50 PM.png > > > As a business analyst I want the ability to review simulation test results so that I can view the accuracy of my rules. > *Verification conditions:* > - CSS styles that employ relevant PatternFly styles and/or patterns, such as: http://www.patternfly.org/pattern-library/data-visualization/donut-chart/... > - CSS that articulates the design wireframe attached, and: > https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476070 > https://docs.google.com/document/d/1I_ghU9An--uQRzuVV9zXB387HLYjZcc01LXFX... > - Reviewed by scrum team prior to PR/dev delivery. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2707) CSS for test results panel/dock design

by Daniele Zonca (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2707?page=com.atlassian.jira.plugi... ] Daniele Zonca edited comment on DROOLS-2707 at 7/16/18 7:41 AM: ---------------------------------------------------------------- [~uxdlc] I think that for now we will only have pass/fail but I'm not sure if in the future we will have more options like "ignored" or similar. I would prefer a layout that can easily support more than two categories EDIT: I think we are able to provide all the requested info in the result panel because all of them are available in JUnit test result or can be easily calculated was (Author: danielezonca): [~uxdlc] I think that for now we will only have pass/fail but I'm not sure if in the future we will have more options like "ignored" or similar. I would prefer a layout that can easily support more than two categories > CSS for test results panel/dock design > -------------------------------------- > > Key: DROOLS-2707 > URL: https://issues.jboss.org/browse/DROOLS-2707 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Sarah Rambacher > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-07-05 at 11.33.41 AM.png, Screen Shot 2018-07-11 at 3.03.50 PM.png > > > As a business analyst I want the ability to review simulation test results so that I can view the accuracy of my rules. > *Verification conditions:* > - CSS styles that employ relevant PatternFly styles and/or patterns, such as: http://www.patternfly.org/pattern-library/data-visualization/donut-chart/... > - CSS that articulates the design wireframe attached, and: > https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476070 > https://docs.google.com/document/d/1I_ghU9An--uQRzuVV9zXB387HLYjZcc01LXFX... > - Reviewed by scrum team prior to PR/dev delivery. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2707) CSS for test results panel/dock design

by Daniele Zonca (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2707?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-2707: --------------------------------------- [~uxdlc] I think that for now we will only have pass/fail but I'm not sure if in the future we will have more options like "ignored" or similar. I would prefer a layout that can easily support more than two categories > CSS for test results panel/dock design > -------------------------------------- > > Key: DROOLS-2707 > URL: https://issues.jboss.org/browse/DROOLS-2707 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Sarah Rambacher > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-07-05 at 11.33.41 AM.png, Screen Shot 2018-07-11 at 3.03.50 PM.png > > > As a business analyst I want the ability to review simulation test results so that I can view the accuracy of my rules. > *Verification conditions:* > - CSS styles that employ relevant PatternFly styles and/or patterns, such as: http://www.patternfly.org/pattern-library/data-visualization/donut-chart/... > - CSS that articulates the design wireframe attached, and: > https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476070 > https://docs.google.com/document/d/1I_ghU9An--uQRzuVV9zXB387HLYjZcc01LXFX... > - Reviewed by scrum team prior to PR/dev delivery. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELY-1607) Revise cipher suites exposed by Elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1607?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1607: --------------------------------------- I think this is definitely a good case to review how we currently document how the databases were initially defined and how they are maintained so future engineers to work on this have a good head start to track down the information needed to verify and apply updates. > Revise cipher suites exposed by Elytron > --------------------------------------- > > Key: ELY-1607 > URL: https://issues.jboss.org/browse/ELY-1607 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.4.0.Final > Reporter: Martin Choma > Assignee: Justin Cook > Priority: Blocker > Fix For: 1.4.1.CR1 > > > I know there have been discussed earlier we should revise/update database and defaults regularly. > Checking few ciphersuites from java cipher suite list [1]. I have noticed: > * Elytron is missing CHACHA20 variants introduced in rfc 7905 > * missing ciphersuites from RFC 6209 > * ... > Please revise content of MechanismDatabase.properties > [1] https://docs.oracle.com/javase/10/docs/specs/security/standard-names.html... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELYWEB-6) Coverity, Dereference null return value ElytronHttpServletExchange

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELYWEB-6?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELYWEB-6: ---------------------------------- Fix Version/s: 1.2.1.CR1 > Coverity, Dereference null return value ElytronHttpServletExchange > ------------------------------------------------------------------ > > Key: ELYWEB-6 > URL: https://issues.jboss.org/browse/ELYWEB-6 > Project: Elytron Web > Issue Type: Bug > Affects Versions: 1.2.0.Final > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Minor > Fix For: 1.2.1.CR1 > > > Javadoc for ServletRequest.getRequestDispatcher(path) [1] says null can be returned. Therefore Coverity detects disp.forward() as potentially dereferencing null code. [2] > [1] https://docs.oracle.com/javaee/6/api/javax/servlet/ServletRequest.html#ge... > [2] https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELY-1609) constraint drive authentication method in undertow doesn't work with elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1609?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1609: ---------------------------------- Fix Version/s: 1.4.1.CR1 > constraint drive authentication method in undertow doesn't work with elytron > ---------------------------------------------------------------------------- > > Key: ELY-1609 > URL: https://issues.jboss.org/browse/ELY-1609 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Affects Versions: 1.4.0.Final > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.4.1.CR1 > > > When elytron is enabled constraint driven authentication method (i.e. proactive-authentication=false) has no effect. > If you try to request an unsecured page sending in an invalid user with basic authentication, you should get the page returned with constraint drive authentication and a 401 with proactive authentication. This is what happens without Elytron enabled. But if you enable Elytron it gives a 401 in both cases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELY-1609) constraint drive authentication method in undertow doesn't work with elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1609?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1609: ---------------------------------- Priority: Critical (was: Major) > constraint drive authentication method in undertow doesn't work with elytron > ---------------------------------------------------------------------------- > > Key: ELY-1609 > URL: https://issues.jboss.org/browse/ELY-1609 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Affects Versions: 1.4.0.Final > Reporter: Darran Lofthouse > Priority: Critical > > When elytron is enabled constraint driven authentication method (i.e. proactive-authentication=false) has no effect. > If you try to request an unsecured page sending in an invalid user with basic authentication, you should get the page returned with constraint drive authentication and a 401 with proactive authentication. This is what happens without Elytron enabled. But if you enable Elytron it gives a 401 in both cases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELY-1609) constraint drive authentication method in undertow doesn't work with elytron

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1609?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse moved JBEAP-15057 to ELY-1609: ----------------------------------------------- Project: WildFly Elytron (was: JBoss Enterprise Application Platform) Key: ELY-1609 (was: JBEAP-15057) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: HTTP (was: Security) (was: Web (Undertow)) Affects Version/s: 1.4.0.Final (was: 7.1.3.GA) > constraint drive authentication method in undertow doesn't work with elytron > ---------------------------------------------------------------------------- > > Key: ELY-1609 > URL: https://issues.jboss.org/browse/ELY-1609 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Affects Versions: 1.4.0.Final > Reporter: Darran Lofthouse > > When elytron is enabled constraint driven authentication method (i.e. proactive-authentication=false) has no effect. > If you try to request an unsecured page sending in an invalid user with basic authentication, you should get the page returned with constraint drive authentication and a 401 with proactive authentication. This is what happens without Elytron enabled. But if you enable Elytron it gives a 401 in both cases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 July 2018