July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4532) Investigate new JDK 13 regressions

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFCORE-4532?page=com.atlassian.jira.plugi... ] Richard Opalka commented on WFCORE-4532: ---------------------------------------- Related issue https://bugs.openjdk.java.net/browse/JDK-8228396 > Investigate new JDK 13 regressions > ---------------------------------- > > Key: WFCORE-4532 > URL: https://issues.jboss.org/browse/WFCORE-4532 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Critical > Labels: jdk13 > > Latest Open JDK 13 Early Access 25 introduced six new regressions in our test suites. > Failing tests in WILDFLY-CORE are: > * wildfly-core/elytron/src/test/java/org/wildfly/extension/elytron/TlsTestCase.java > * wildfly-core/testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/sasl/mgmt/KerberosHttpMgmtSaslTestCase.java > * wildfly-core/testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/sasl/mgmt/KerberosNativeMgmtSaslTestCase.java > Failing tests in WILDFLY are: > * wildfly/testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/web/ssl/CertificateRolesLoginModuleTestCase.java > * wildfly/testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/web/ssl/DatabaseCertLoginModuleTestCase.java > * wildfly/testsuite/integration/manualmode/src/test/java/org/jboss/as/test/manualmode/web/ssl/HTTPSWebConnectorTestCase.java > Could somebody from our security team have a look what is going on [~darran] ? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2602) Download link for particular KIE Execution Server war instead of zip with wars for all containers

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-2602?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer closed DROOLS-2602. ------------------------------------------ Resolution: Done > Download link for particular KIE Execution Server war instead of zip with wars for all containers > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-2602 > URL: https://issues.jboss.org/browse/DROOLS-2602 > Project: Drools > Issue Type: Feature Request > Components: kie server > Affects Versions: 7.7.0.Final > Reporter: Igor Azarny > Assignee: Michael Biarnes Kiefer > Priority: Optional > Labels: distribution > > Could you please provide the download link for particular KIE Execution Server war instead of zip with wars for all containers? > Reason - need to create buildpack with kie server for pivotal cloud foundry on CI env. So I need just kie-server-7.7.0.Final-webc.war instead of kie-server-distribution-7.7.0.Final.zip > Thanks, Igor -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2357) ConnectException error messages when using TCP protocol

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2357?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2357. ---------------------------- Resolution: Done > ConnectException error messages when using TCP protocol > ------------------------------------------------------- > > Key: JGRP-2357 > URL: https://issues.jboss.org/browse/JGRP-2357 > Project: JGroups > Issue Type: Bug > Reporter: Dante Wang > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.2 > > > When using TCP protocol with JGroups 4.1.1 Final, various kinds of java.net.ConnectException error messages occasionally appear in the log. These exception log messages were by default suppressed with logging level "TRACE" before JGRP-2332 (commit 538a5431b8fd06d644a72f48d584f8114f26a295). > The ConnectExceptions in this case happen upon attempts to discover nodes, verify node status when another node dies and send ACK when another node leaves. > The ConnectException messages of node discovery can be avoided by carefully changing configuration of TCPPING or using other ping like JDBC_PING. But the two kinds of messages upon node exiting seem to have no way to avoid. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2357) ConnectException error messages when using TCP protocol

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2357?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2357: -------------------------------- The problem is that the bundler which sends messages runs on a separate thread; I cannot just catch exceptions in TCPPING that are caused by non-existant members. Hmm, I changed the ERROR log message back to TRACE. OTOH, this prevents people from seeing real (serious) errors, ie. caused by misconfiguration. In this case, they have to enable TRACE level logging for the transport. > ConnectException error messages when using TCP protocol > ------------------------------------------------------- > > Key: JGRP-2357 > URL: https://issues.jboss.org/browse/JGRP-2357 > Project: JGroups > Issue Type: Bug > Reporter: Dante Wang > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.2 > > > When using TCP protocol with JGroups 4.1.1 Final, various kinds of java.net.ConnectException error messages occasionally appear in the log. These exception log messages were by default suppressed with logging level "TRACE" before JGRP-2332 (commit 538a5431b8fd06d644a72f48d584f8114f26a295). > The ConnectExceptions in this case happen upon attempts to discover nodes, verify node status when another node dies and send ACK when another node leaves. > The ConnectException messages of node discovery can be avoided by carefully changing configuration of TCPPING or using other ping like JDBC_PING. But the two kinds of messages upon node exiting seem to have no way to avoid. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-775) Identify uncovered areas

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-775?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-775. --------------------------------- Resolution: Done Added for UI tests https://issues.jboss.org/browse/SWSQE-879 > Identify uncovered areas > ------------------------ > > Key: SWSQE-775 > URL: https://issues.jboss.org/browse/SWSQE-775 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > > We have the code coverage report so we should be able to identify uncovered areas and create tasks to implement automation. > Also we need to check if all files in the report are expected (remove mock/test data files) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2357) ConnectException error messages when using TCP protocol

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2357?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2357: --------------------------- Fix Version/s: 4.1.2 > ConnectException error messages when using TCP protocol > ------------------------------------------------------- > > Key: JGRP-2357 > URL: https://issues.jboss.org/browse/JGRP-2357 > Project: JGroups > Issue Type: Bug > Reporter: Dante Wang > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.2 > > > When using TCP protocol with JGroups 4.1.1 Final, various kinds of java.net.ConnectException error messages occasionally appear in the log. These exception log messages were by default suppressed with logging level "TRACE" before JGRP-2332 (commit 538a5431b8fd06d644a72f48d584f8114f26a295). > The ConnectExceptions in this case happen upon attempts to discover nodes, verify node status when another node dies and send ACK when another node leaves. > The ConnectException messages of node discovery can be avoided by carefully changing configuration of TCPPING or using other ping like JDBC_PING. But the two kinds of messages upon node exiting seem to have no way to avoid. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-897) Increase code coverage above 80% for github.com/kiali/kiali/util/intutil (UI tests)

by Filip Brychta (Jira)

Filip Brychta created SWSQE-897: ----------------------------------- Summary: Increase code coverage above 80% for github.com/kiali/kiali/util/intutil (UI tests) Key: SWSQE-897 URL: https://issues.jboss.org/browse/SWSQE-897 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Read parent task for details. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-894) Increase code coverage above 80% for github.com/kiali/kiali/status (UI tests)

by Filip Brychta (Jira)

Filip Brychta created SWSQE-894: ----------------------------------- Summary: Increase code coverage above 80% for github.com/kiali/kiali/status (UI tests) Key: SWSQE-894 URL: https://issues.jboss.org/browse/SWSQE-894 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Read parent task for details. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-896) Increase code coverage above 80% for github.com/kiali/kiali/util/httputil (UI tests)

by Filip Brychta (Jira)

Filip Brychta created SWSQE-896: ----------------------------------- Summary: Increase code coverage above 80% for github.com/kiali/kiali/util/httputil (UI tests) Key: SWSQE-896 URL: https://issues.jboss.org/browse/SWSQE-896 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Read parent task for details. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-895) Increase code coverage above 80% for github.com/kiali/kiali/util (UI tests)

by Filip Brychta (Jira)

Filip Brychta created SWSQE-895: ----------------------------------- Summary: Increase code coverage above 80% for github.com/kiali/kiali/util (UI tests) Key: SWSQE-895 URL: https://issues.jboss.org/browse/SWSQE-895 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Read parent task for details. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2019