May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4059) Unable to test dmn context

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4059?page=com.atlassian.jira.plugi... ] Daniele Zonca resolved DROOLS-4059. ----------------------------------- Resolution: Done Fixed by https://issues.jboss.org/browse/DROOLS-3806 > Unable to test dmn context > -------------------------- > > Key: DROOLS-4059 > URL: https://issues.jboss.org/browse/DROOLS-4059 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.22.0.Final > Reporter: Jozef Marko > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > Attachments: Screenshot from 2019-05-21 10-37-01.png, Screenshot from 2019-05-21 10-37-22.png, dmn.zip > > > There is issue with scenario, that verifies dmn context. The attached scenario was created in the way shown in the picture. From the dialog with expected and actual value I clicked *Apply* button to fix scenarios. However after rerun, there is exception that value can not be parsed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12137) Upgrade MP Metrics to 2.0-1.0.0

by Sverre Boschman (Jira)

Sverre Boschman created WFLY-12137: -------------------------------------- Summary: Upgrade MP Metrics to 2.0-1.0.0 Key: WFLY-12137 URL: https://issues.jboss.org/browse/WFLY-12137 Project: WildFly Issue Type: Component Upgrade Components: MP Metrics Reporter: Sverre Boschman Assignee: Jeff Mesnil Upgrade MP Metrics to 2.0-1.0.0 Details about spec 2.0: https://github.com/eclipse/microprofile-metrics/releases/download/2.0.0/m... https://github.com/eclipse/microprofile-metrics/releases/download/2.0.0/c... Details about smallrye 2.0-1.0.0: https://github.com/smallrye/smallrye-metrics/issues/96 https://github.com/smallrye/smallrye-metrics/issues/110 Tag: https://github.com/smallrye/smallrye-metrics/releases/tag/smallrye-metric... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1689) Rewrite HttpAuthenticator$AuthenticationExchange.authenticate() to use a recursive call.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1689?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1689: --------------------------------------- May delay this one whilst looking at alternative issues, one issue here is we want the responders to be called in the same order the mechanisms were originally called this is especially important if mechanisms are adding the same headers where header ordering can have meaning. > Rewrite HttpAuthenticator$AuthenticationExchange.authenticate() to use a recursive call. > ---------------------------------------------------------------------------------------- > > Key: ELY-1689 > URL: https://issues.jboss.org/browse/ELY-1689 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.10.0.CR1 > > > By switching to a recursive call we can eliminate the intermediate ArrayList which is required to hold the responders. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3992) Improving error messages from backend to cell popover

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-3992?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-3992: ------------------------------- Issue Type: Enhancement (was: Bug) > Improving error messages from backend to cell popover > ------------------------------------------------------ > > Key: DROOLS-3992 > URL: https://issues.jboss.org/browse/DROOLS-3992 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.22.0.Final > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Minor > Labels: ScenarioSimulation > > Aim of this ticket: > - Improve error messages sent by server to the cell popover in case of specific errors: eg. > [~kkufova]: I noticed that Impossible to parse as boolean message keeps getting displayed instead of an actual help. For example, I used falsee instead of false. I think in this case we definitely need The expected value is 'false' but the actual one is 'falsee'. Another scenario: if the expected value is null but I enter [] instead, the error message is Error with this value: Impossible to parse as boolean. It doesn't say anything about the actual value being null. > - Improving exceptions handling related to this part: at the moment, any type of exception could be sent to the popover (eg. OutOfMemory). Only a subset should be managed. > Related to https://issues.jboss.org/browse/DROOLS-3838 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-162) IllegalStateException when TrustManager with SunX509 algorithm and with OCSP

by Martin Mazanek (Jira)

[ https://issues.jboss.org/browse/WFWIP-162?page=com.atlassian.jira.plugin.... ] Martin Mazanek commented on WFWIP-162: -------------------------------------- Actually, this behavior is correct. Revocation requires PKIX compatible TrustManagerFactory, and SunX509 isn't. It is mostly backward compatibility algorithm and PKIX should be used instead. But I will add better description for the exception, as this is obviously very confusing. > IllegalStateException when TrustManager with SunX509 algorithm and with OCSP > ---------------------------------------------------------------------------- > > Key: WFWIP-162 > URL: https://issues.jboss.org/browse/WFWIP-162 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Environment: WildFly built with following branches in use: > {code} > https://github.com/nekdozjam/wildfly-elytron/tree/ELY-1617 > https://github.com/nekdozjam/wildfly-core/tree/WFCORE-3947 > {code} > Reporter: Jan Stourac > Assignee: Martin Mazanek > Priority: Major > Attachments: ocsp-truststore.jks > > > I can see an error when I try to create 'trust-manager' with OCSP enabled and SunX509 algorithm specified. When I don't specify SunX509 algorithm, operation succeeds. > Here are noticed error messages: > {code} > { > "outcome" => "failed", > "failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.trust-manager.tm" => "Failed to start service > Caused by: java.lang.IllegalStateException: ELY04026: Could not create trust manager [org.wildfly.security.ssl.X509RevocationTrustManager] > Caused by: java.security.InvalidAlgorithmParameterException: SunX509 TrustManagerFactory does not use ManagerFactoryParameters"}}, > "rolled-back" => true > } > {code} > In server.log, there is following text: > {code} > 17:14:48,560 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service org.wildfly.security.trust-manager.tm: org.jboss.msc.service.StartException in service org.wildfly.security.trust-manager.tm: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException: ELY04026: Could not create trust manager [org.wildfly.security.ssl.X509RevocationTrustManager] > at org.wildfly.security.ssl.X509RevocationTrustManager.<init>(X509RevocationTrustManager.java:108) > at org.wildfly.security.ssl.X509RevocationTrustManager.<init>(X509RevocationTrustManager.java:56) > at org.wildfly.security.ssl.X509RevocationTrustManager$Builder.build(X509RevocationTrustManager.java:293) > at org.wildfly.extension.elytron.SSLDefinitions$2.lambda$createX509RevocationExtendedTrustManager$1(SSLDefinitions.java:732) > at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700) > ... 6 more > Caused by: java.security.InvalidAlgorithmParameterException: SunX509 TrustManagerFactory does not use ManagerFactoryParameters > at sun.security.ssl.TrustManagerFactoryImpl$SimpleFactory.getInstance(TrustManagerFactoryImpl.java:257) > at sun.security.ssl.TrustManagerFactoryImpl.engineInit(TrustManagerFactoryImpl.java:90) > at javax.net.ssl.TrustManagerFactory.init(TrustManagerFactory.java:273) > at org.wildfly.security.ssl.X509RevocationTrustManager.<init>(X509RevocationTrustManager.java:98) > ... 12 more > 17:14:48,562 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("trust-manager" => "tm") > ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.trust-manager.tm" => "Failed to start service > Caused by: java.lang.IllegalStateException: ELY04026: Could not create trust manager [org.wildfly.security.ssl.X509RevocationTrustManager] > Caused by: java.security.InvalidAlgorithmParameterException: SunX509 TrustManagerFactory does not use ManagerFactoryParameters"}} > {code} > I'm attaching kestore file that I used for this. Password is 'weneedthatforjava'. > Note that when I try 'certificate-revocation-list' instead or if I omit 'algorithm' attribute at all, the operation succeeds. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-765) Documentation of code coverage

by Filip Brychta (Jira)

Filip Brychta created SWSQE-765: ----------------------------------- Summary: Documentation of code coverage Key: SWSQE-765 URL: https://issues.jboss.org/browse/SWSQE-765 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta Document how the code coverage is done. Demo it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-702) Report code coverage for system tests in jenkins job via cobertura plugin

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-702?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-702: ------------------------------------- Done for UI tests https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/python-ui-tests... > Report code coverage for system tests in jenkins job via cobertura plugin > ------------------------------------------------------------------------- > > Key: SWSQE-702 > URL: https://issues.jboss.org/browse/SWSQE-702 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > https://docs.engineering.redhat.com/display/CentralCI/Golang+Code+Coverag... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-702) Report code coverage for system tests in jenkins job via cobertura plugin

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-702?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-702. --------------------------------- Resolution: Done > Report code coverage for system tests in jenkins job via cobertura plugin > ------------------------------------------------------------------------- > > Key: SWSQE-702 > URL: https://issues.jboss.org/browse/SWSQE-702 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > https://docs.engineering.redhat.com/display/CentralCI/Golang+Code+Coverag... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-764) Create OCP 4.1 clusters in PSI when it's GA

by Filip Brychta (Jira)

Filip Brychta created SWSQE-764: ----------------------------------- Summary: Create OCP 4.1 clusters in PSI when it's GA Key: SWSQE-764 URL: https://issues.jboss.org/browse/SWSQE-764 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta We need to create OCP 4.1 clusters in PSI for kiali testing. 4.1 should be GA Jun 3th -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-764) Create OCP 4.1 clusters in PSI when it's GA

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-764?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-764: -------------------------------- Sprint: Kiali Sprint #23 > Create OCP 4.1 clusters in PSI when it's GA > ------------------------------------------- > > Key: SWSQE-764 > URL: https://issues.jboss.org/browse/SWSQE-764 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We need to create OCP 4.1 clusters in PSI for kiali testing. 4.1 should be GA Jun 3th -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 May 2019