August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10873) Duplicated httpcomponent jars in WF 14.0.0.Beta2

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10873?page=com.atlassian.jira.plugin... ] Rostislav Svoboda commented on WFLY-10873: ------------------------------------------ https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/src... > Duplicated httpcomponent jars in WF 14.0.0.Beta2 > ------------------------------------------------ > > Key: WFLY-10873 > URL: https://issues.jboss.org/browse/WFLY-10873 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 14.0.0.Beta2 > Reporter: Martin Švehla > Assignee: Jason Greene > > In current Beta2 build, I see duplicated httpclient and httpcore jars. The new org.apache.httpcomponents.core module was added that introduced this duplication. > in 14.0.0.Beta2: > {code} > $ tree modules/system/layers/base/org/apache/httpcomponents/ > modules/system/layers/base/org/apache/httpcomponents/ > ├── core > │ └── main > │ ├── httpclient-4.5.2.jar > │ ├── httpcore-4.4.4.jar > │ └── module.xml > └── main > ├── httpasyncclient-4.1.3.jar > ├── httpclient-4.5.2.jar > ├── httpcore-4.4.4.jar > ├── httpcore-nio-4.4.4.jar > ├── httpmime-4.5.2.jar > └── module.xml > {code} > In WF 13.0.0.Final > {code} > $ tree modules/system/layers/base/org/apache/httpcomponents/ > modules/system/layers/base/org/apache/httpcomponents/ > └── main > ├── httpasyncclient-4.1.3.jar > ├── httpclient-4.5.2.jar > ├── httpcore-4.4.4.jar > ├── httpcore-nio-4.4.4.jar > ├── httpmime-4.5.2.jar > └── module.xml > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-380) Bookinfo Deploy Failing

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-380: ---------------------------------- Summary: Bookinfo Deploy Failing Key: SWSQE-380 URL: https://issues.jboss.org/browse/SWSQE-380 Project: Kiali QE Issue Type: Bug Reporter: Matt Mahoney Assignee: Guilherme Baufaker Rêgo [istio] $ ansible-playbook bookinfo.yml -e istio_version=1.0.0 -e traffic_generator=true -e ingress_route=false -e rate=1 -v Using /etc/ansible/ansible.cfg as config file [WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all' ERROR! Syntax Error while loading YAML. mapping values are not allowed in this context The error appears to have been in '/home/jenkins/workspace/install-bookinfo/checkout-directory/scripts/istio/bookinfo.yml': line 13, column 15, -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-65) [Artemis 2.x upgrade] Artemis RA connections disconnected after failover

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-65?page=com.atlassian.jira.plugin.s... ] Clebert Suconic commented on WFWIP-65: -------------------------------------- [~mnovak] that is a different test... the issue seems around quorum. Are you sure this is not a different issue.. and are you sure this is a regression? > [Artemis 2.x upgrade] Artemis RA connections disconnected after failover > ------------------------------------------------------------------------- > > Key: WFWIP-65 > URL: https://issues.jboss.org/browse/WFWIP-65 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Clebert Suconic > Priority: Blocker > Labels: feature-branch-blocker > Attachments: DedicatedFailoverTestCaseWithMdb.testShutdownWithFailback.zip > > > There is regression againt Artemis 1.5.5.0012 in scenario with failover of Artemis RA from live to backup (shared store, dedicated topology). After backup activates after failover, connections of RA does not failover to backup (or are disconnected from backup just after failover) > Test scenario: > * There are three servers. Live server (Node 1) and backupserver (Node 2) are in dedicated HA topology. > * InQueue and OutQueue are deployed on live and backup. Send messages to InQueue on live server. > * When all messages are sent, deploy message driven bean on Node 3. > * MDB sends messages form InQueue to OutQueue. > * Shutdown live server. Wait for backup server to alive, then start live server again and stop backup. > * Receive messages from OutQueue from live server. > Results: > After live server is stopped and backup activates, no messages are processed by MDB. Looking at trace logs it seems that MDB does reconnect to backup but it's then disconnected. Then I don't see connector to backup server between tried connectors during reconnection. > Attaching reproduce and logs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1639) FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1639?page=com.atlassian.jira.plugin.s... ] Martin Choma edited comment on ELY-1639 at 8/17/18 8:43 AM: ------------------------------------------------------------ I can confirm I am able to perform 2-way SSL handshake in FIPS mode using PKCS11 with {{<key-store-ssl-certificate algorithm="SunX509" key-store-name="keystore"/>}} But when I try to use alias attribute I get {code} 14:41:49,973 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: java.lang.ExceptionInInitializerError at org.wildfly.security.auth.client.AuthenticationContext.lambda$static$0(AuthenticationContext.java:54) at org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:286) at org.wildfly.security.auth.client.AuthenticationContext.captureCurrent(AuthenticationContext.java:86) at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:146) at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85) at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222) at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203) at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198) at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328) at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291) at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45) at org.jboss.modules.Module.run(Module.java:352) at org.jboss.modules.Module.run(Module.java:320) at org.jboss.modules.Main.main(Main.java:593) Caused by: org.wildfly.security.auth.client.InvalidAuthenticationConfigurationException: org.wildfly.client.config.ConfigXMLParseException: ELY01167: Specifying alias is allowed only when used built-in KeyManager at file:///home/mchoma/git-repo/tests-security/fips/target/CliClientTestCase/cli-test-wildfly-config-835240841338108754.xml:13:17 at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:40) at java.security.AccessController.doPrivileged(Native Method) at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.<clinit>(DefaultAuthenticationContextProvider.java:36) ... 14 more Caused by: org.wildfly.client.config.ConfigXMLParseException: ELY01167: Specifying alias is allowed only when used built-in KeyManager at file:///home/mchoma/git-repo/tests-security/fips/target/CliClientTestCase/cli-test-wildfly-config-835240841338108754.xml:13:17 at org.wildfly.security.auth.client.ElytronXmlParser.parseKeyStoreSslCertificate(ElytronXmlParser.java:750) at org.wildfly.security.auth.client.ElytronXmlParser.parseSslContextType(ElytronXmlParser.java:446) at org.wildfly.security.auth.client.ElytronXmlParser.parseSslContextsType(ElytronXmlParser.java:402) at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:315) at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:236) at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:197) at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38) ... 16 more {code} was (Author: mchoma): I can confirm I am able to perform 2-way SSL handshake in FIPS mode using PKCS11 with {{<key-store-ssl-certificate algorithm="SunX509" key-store-name="keystore"/>}} > FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used > ------------------------------------------------------------- > > Key: ELY-1639 > URL: https://issues.jboss.org/browse/ELY-1639 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Blocker > Attachments: cli-wildfly-config.xml > > > Fix of ELY-1622 introduced regression. It is not possible to do 1 way ssl (no key-store-ssl-certificate in wildfly-config.xml) with exception > {code} > 14:13:56,143 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45) > at org.jboss.modules.Module.run(Module.java:352) > at org.jboss.modules.Module.run(Module.java:320) > at org.jboss.modules.Main.main(Main.java:593) > Caused by: org.jboss.as.cli.CommandLineException: Failed to resolve host 'localhost' > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1256) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328) > ... 5 more > Caused by: java.io.IOException: Failed to obtain SSLContext > at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:156) > at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222) > ... 8 more > Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used > at sun.security.ssl.SSLContextImpl.chooseKeyManager(SSLContextImpl.java:149) > at sun.security.ssl.SSLContextImpl.engineInit(SSLContextImpl.java:66) > at javax.net.ssl.SSLContext.init(SSLContext.java:282) > at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:372) > at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53) > at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:221) > at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:208) > at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:153) > ... 10 more > {code} > It is because after fix Fix of ELY-1622 custom keymanager is used. But it is forbidden by jdk FIPS PKCS11. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-87) [Artemis 2.x upgrade] Transaction remained in prepared state after failover of MDB

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFWIP-87?page=com.atlassian.jira.plugin.s... ] Clebert Suconic reassigned WFWIP-87: ------------------------------------ Assignee: Clebert Suconic (was: Justin Bertram) > [Artemis 2.x upgrade] Transaction remained in prepared state after failover of MDB > ---------------------------------------------------------------------------------- > > Key: WFWIP-87 > URL: https://issues.jboss.org/browse/WFWIP-87 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Clebert Suconic > Priority: Blocker > > There is regression in test scenario where MDB failovers from live to backup. Live is cleanly shutdown. > Problem is that after MDB failovers to backup then there is still transaction in prepared state which survive periodic recovery cycles. > Link to build: > https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2678) The ability to upload an external spreadsheet

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2678?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2678: --------------------------------- Sprint: 2018 Week 36-38 > The ability to upload an external spreadsheet > --------------------------------------------- > > Key: DROOLS-2678 > URL: https://issues.jboss.org/browse/DROOLS-2678 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > > As a business user I want the ability to upload an external spreadsheet so that I can speed up scenario data input. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2680) Run a single row scenario test

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2680?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2680: --------------------------------- Sprint: 2018 Week 36-38 > Run a single row scenario test > ------------------------------ > > Key: DROOLS-2680 > URL: https://issues.jboss.org/browse/DROOLS-2680 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > Priority: Minor > > As a business analyst I want to run a single row scenario test so that I can run only one test when I have too many rows in the scenario test. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1639) FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1639?page=com.atlassian.jira.plugin.s... ] Martin Choma commented on ELY-1639: ----------------------------------- I can confirm I am able to perform 2-way SSL handshake in FIPS mode using PKCS11 with {{<key-store-ssl-certificate algorithm="SunX509" key-store-name="keystore"/>}} > FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used > ------------------------------------------------------------- > > Key: ELY-1639 > URL: https://issues.jboss.org/browse/ELY-1639 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Blocker > Attachments: cli-wildfly-config.xml > > > Fix of ELY-1622 introduced regression. It is not possible to do 1 way ssl (no key-store-ssl-certificate in wildfly-config.xml) with exception > {code} > 14:13:56,143 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45) > at org.jboss.modules.Module.run(Module.java:352) > at org.jboss.modules.Module.run(Module.java:320) > at org.jboss.modules.Main.main(Main.java:593) > Caused by: org.jboss.as.cli.CommandLineException: Failed to resolve host 'localhost' > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1256) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328) > ... 5 more > Caused by: java.io.IOException: Failed to obtain SSLContext > at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:156) > at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222) > ... 8 more > Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used > at sun.security.ssl.SSLContextImpl.chooseKeyManager(SSLContextImpl.java:149) > at sun.security.ssl.SSLContextImpl.engineInit(SSLContextImpl.java:66) > at javax.net.ssl.SSLContext.init(SSLContext.java:282) > at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:372) > at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53) > at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:221) > at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:208) > at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:153) > ... 10 more > {code} > It is because after fix Fix of ELY-1622 custom keymanager is used. But it is forbidden by jdk FIPS PKCS11. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2784) CSS for test "expression builder" dock tab design

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2784?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2784: --------------------------------- Sprint: 2018 Week 36-38 > CSS for test "expression builder" dock tab design > ------------------------------------------------- > > Key: DROOLS-2784 > URL: https://issues.jboss.org/browse/DROOLS-2784 > 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-24 at 9.19.37 AM.png, Screen Shot 2018-07-27 at 12.41.52 PM.png > > > As a practitioner I want to the option to an expression builder within the UI to: > - search for and select from a set of hierarchical Data Objects > - set conditions > - name variables > so that I can add these selections as Given/Expect input values when creating a scenario test outline. > *Verification conditions:* > - CSS styles that employ relevant PatternFly styles. > - CSS that articulates the design wireframe attached, and: > https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476075, and: > 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)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2679) Run a single scenario test

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2679?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2679: --------------------------------- Sprint: 2018 Week 36-38 > Run a single scenario test > -------------------------- > > Key: DROOLS-2679 > URL: https://issues.jboss.org/browse/DROOLS-2679 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Daniele Zonca > > As a business analyst I want to run a single scenario test so that I can view the accuracy of my rules. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018