October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12641) Add test module using microprofile-jwt TCK

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-12641: --------------------------------------- Summary: Add test module using microprofile-jwt TCK Key: WFLY-12641 URL: https://issues.jboss.org/browse/WFLY-12641 Project: WildFly Issue Type: Sub-task Components: Security, Test Suite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 19.0.0.Beta1 Additional integration tests will be added but the TCK is a good start. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12640) JSFFailoverTestCase fails intermittently

by Ondrej Kotek (Jira)

Ondrej Kotek created WFLY-12640: ----------------------------------- Summary: JSFFailoverTestCase fails intermittently Key: WFLY-12640 URL: https://issues.jboss.org/browse/WFLY-12640 Project: WildFly Issue Type: Bug Components: Clustering, Test Suite Affects Versions: 15.0.0.Beta1 Reporter: Ondrej Kotek Assignee: Radoslav Husar Fix For: 15.0.0.Final Tests of the {{org.jboss.as.test.clustering.cluster.jsf.JSFFailoverTestCase}} test case fail intermittently. testGracefulSimpleFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=3970377990724... testGracefulUndeployFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=-717823432939... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-186) PVC access mode is hardcoded to ReadWriteOnce

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-186?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-186: ----------------------------------- tracked by https://github.com/wildfly/wildfly-operator/issues/103 > PVC access mode is hardcoded to ReadWriteOnce > --------------------------------------------- > > Key: WFWIP-186 > URL: https://issues.jboss.org/browse/WFWIP-186 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > Setting different access mode (ReadWriteMany, ReadOnlyMany) is ignored > [1] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-184) Can't specify arbitrary Persistent Volume Claim Name

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-184?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-184: ----------------------------------- tracked by https://github.com/wildfly/wildfly-operator/issues/103 > Can't specify arbitrary Persistent Volume Claim Name > ---------------------------------------------------- > > Key: WFWIP-184 > URL: https://issues.jboss.org/browse/WFWIP-184 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > Labels: operator > > I cant create PVC with arbitrary name. It must be empty [3] or "<CR name>-volume" [2] > When I specify PVC name I get error like > {code} > create Pod simple-jaxrs-eap72-0 in StatefulSet simple-jaxrs-eap72 failed error: Pod "simple-jaxrs-eap72-0" is invalid: spec.containers[0].volumeMounts[0].name: Not found: "simple-jaxrs-eap72-volume" > {code} > Is there any reason to not permit arbitrary PVC name? > [1] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi... > [2] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi... > [3] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2390) New NO-based transports

by Bela Ban (Jira)

Bela Ban created JGRP-2390: ------------------------------ Summary: New NO-based transports Key: JGRP-2390 URL: https://issues.jboss.org/browse/JGRP-2390 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0 Based on one-nio (https://github.com/odnoklassniki/one-nio) or Netty (https://github.com/netty/netty/pull/9509) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-199) Operator default values

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-199?page=com.atlassian.jira.plugin.... ] Jeff Mesnil resolved WFWIP-199. ------------------------------- Resolution: Done Fixed upstream by https://github.com/wildfly/wildfly-operator/pull/81 > Operator default values > ----------------------- > > Key: WFWIP-199 > URL: https://issues.jboss.org/browse/WFWIP-199 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > Labels: operator > > How should user find default values of parameters? > E.g. for disableHTTPRoute and sessionAffinity. I couldn't find it in api doc [1]. > Looking into CRD [2] I can't see defaults neither. So can user assume default is false? > Could it be somewhere declared explicitly? I think best would be CRD or at leas api doc. > [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#wil... > [2] https://github.com/wildfly/wildfly-operator/blob/master/deploy/crds/wildf... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12639) RemoteStatefulEJBConcurrentFailoverTestCase is unreliable

by Ondrej Kotek (Jira)

Ondrej Kotek created WFLY-12639: ----------------------------------- Summary: RemoteStatefulEJBConcurrentFailoverTestCase is unreliable Key: WFLY-12639 URL: https://issues.jboss.org/browse/WFLY-12639 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Ondrej Kotek Assignee: Radoslav Husar Fix For: 15.0.0.Final Test is failing regularly. https://ci.wildfly.org/project.html?projectId=WF&buildTypeId=&tab=testDet... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12638) StatefulFailoverTestCase fails intermittently

by Ondrej Kotek (Jira)

Ondrej Kotek created WFLY-12638: ----------------------------------- Summary: StatefulFailoverTestCase fails intermittently Key: WFLY-12638 URL: https://issues.jboss.org/browse/WFLY-12638 Project: WildFly Issue Type: Bug Components: Clustering, Test Suite Affects Versions: 15.0.0.Beta1 Environment: Any Reporter: Ondrej Kotek Assignee: Radoslav Husar Fix For: 16.0.0.Beta1, 16.0.0.Final The tests of {{org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase}} occasionally fail, for example: {noformat} [ERROR] Failures: [ERROR] StatefulFailoverTestCase.jmsConnectionFactoryFailover:166->failover:193->queryCount:315 expected:<200> but was:<500> [ERROR] StatefulFailoverTestCase.nestedBeanFailover:286->queryCount:315 expected:<200> but was:<500> [ERROR] StatefulFailoverTestCase.noFailover:117 expected:<1> but was:<3> {noformat} or {noformat} [ERROR] Failures: [ERROR] StatefulFailoverTestCase.nestedBeanFailover:286->queryCount:315 expected:<200> but was:<500> [ERROR] StatefulFailoverTestCase.noFailover:117->queryCount:315 expected:<200> but was:<500> [ERROR] StatefulFailoverTestCase.simpleFailover:145->failover:193->queryCount:315 expected:<200> but was:<500> {noformat} connectionFactoryFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=-822829635945... noFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=-574944609062... jmsConnectionFactoryFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=3564603678560... simpleFailover: https://ci.wildfly.org/project.html?projectId=WF&testNameId=4824753507849... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2380) Sometimes cluster members are not discovered when using TCPGOSSIP

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2380?page=com.atlassian.jira.plugin.... ] Bela Ban closed JGRP-2380. -------------------------- Resolution: Cannot Reproduce Closing this for now. Please re-open if you can provide me a reproducer. > Sometimes cluster members are not discovered when using TCPGOSSIP > ----------------------------------------------------------------- > > Key: JGRP-2380 > URL: https://issues.jboss.org/browse/JGRP-2380 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.19 > Reporter: Pavlo Fedyna > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1.6 > > Attachments: jgroups.xml, logs_failure.txt, logs_success.txt > > > Sometimes new member can't join existing cluster if TCPGOSSIP is used with use_nio property set to true. In such case new member creates its own cluster with only one member of itself. After some period of time MERGE3 protocol merges these two clusters into one, but if min_interval/max_interval values are large, it may take a while. > For some reason, first try of initial discovery always finishes due to join_timeout. In this case only a few members are discovered with no coordinator. > If we are lucky enough, GMS prints following log message: "I (WO-KIT-967-28892) am not the first of the nodes, waiting for another client to become coordinator" and makes second attempt to join cluster which now takes a few milliseconds and succeeds (see logs_success.txt). In case of failure, GMS prints "I (WO-KIT-967-14786) am the first of the nodes, will become coordinator" and creates new cluster with only one member (see logs_failure.txt). > The expectations are that first try of the initial discovery should not fail due to the timeout and it should be as fast as the second one is. > Workaround: set use_nio to false (or just remove it from the stack configuration) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12637) Domain test failures on IBM8 - IllegalStateException: The LogManager was not properly installed

by Ondrej Kotek (Jira)

Ondrej Kotek created WFLY-12637: ----------------------------------- Summary: Domain test failures on IBM8 - IllegalStateException: The LogManager was not properly installed Key: WFLY-12637 URL: https://issues.jboss.org/browse/WFLY-12637 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Ondrej Kotek Assignee: James Perkins Fix For: 15.0.0.Beta1, 15.0.0.Final org.jboss.as.test.integration.domain.suites.DeploymentOverlayTestCase#testDeploymentOverlayInDomainMode and org.jboss.as.test.integration.domain.suites.ReadEnvironmentVariablesTestCase#testReadEnvironmentVariablesForServers from domain module of Wildfly testsuite fails on the latest IBM 8 jdk with java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") *reproduce* {noformat} wildfly/testsuite]$ mvn test -DtestLogToFile=false -pl domain -Dts.domain -Dtest=ReadEnvironmentVariablesTestCase,DeploymentOverlayTestCase ... [ERROR] Errors: [ERROR] DeploymentOverlayTestCase.testDeploymentOverlayInDomainMode:300->performHttpCall:340 » NoClassDefFound [ERROR] ReadEnvironmentVariablesTestCase.testReadEnvironmentVariablesForServers:109->getEnvironmentVariables:148 » ExceptionInInitializer [INFO] [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0 {noformat} *Failure message* {noformat} java.lang.ExceptionInInitializerError at java.lang.J9VMInternals.ensureError(J9VMInternals.java:146) at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:135) at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:316) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:329) at org.apache.http.conn.ssl.DefaultHostnameVerifier.<init>(DefaultHostnameVerifier.java:72) at org.apache.http.impl.client.HttpClientBuilder.build(HttpClientBuilder.java:955) at org.apache.http.impl.client.HttpClients.createDefault(HttpClients.java:58) at org.jboss.as.test.integration.domain.suites.ReadEnvironmentVariablesTestCase.getEnvironmentVariables(ReadEnvironmentVariablesTestCase.java:148) at org.jboss.as.test.integration.domain.suites.ReadEnvironmentVariablesTestCase.testReadEnvironmentVariablesForServers(ReadEnvironmentVariablesTestCase.java:109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:508) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:379) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:340) at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:413) Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") at org.jboss.logmanager.Logger.getLogger(Logger.java:57) at org.apache.commons.logging.JBossLogFactory.<init>(JBossLogFactory.java:48) at org.apache.commons.logging.LogFactory$Holder.<clinit>(LogFactory.java:42) ... 44 more {noformat} *Environment* {noformat} $ mvn -version Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) Maven home: /qa/tools/opt/maven3-latest Java version: 1.8.0_171, vendor: IBM Corporation Java home: /qa/tools/opt/x86_64/ibm-java-x86_64-sdk-8.0-5.15/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.10.0-862.el7.x86_64", arch: "amd64", family: "unix" --- $ java -version java version "1.8.0_171" Java(TM) SE Runtime Environment (build 8.0.5.15 - pxa6480sr5fp15-20180502_01(SR5 FP15)) IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180425_385365 (JIT enabled, AOT enabled) OpenJ9 - a7ffbfe OMR - a531219 IBM - 59ef3dc) JCL - 20180425_01 based on Oracle jdk8u171-b11 {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 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 October 2019