September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-5143) Bouncycastle - Failing tests in RESTEasy TS

by Alessio Soldano (Jira)

[ https://issues.redhat.com/browse/WFCORE-5143?page=com.atlassian.jira.plug... ] Alessio Soldano commented on WFCORE-5143: ----------------------------------------- Actually I think there's a bug in WFLY, org.bouncycastle.bcpkix module is missing a dependency to org.bouncycastle.bcprov module. I'll send I PR later. > Bouncycastle - Failing tests in RESTEasy TS > ------------------------------------------- > > Key: WFCORE-5143 > URL: https://issues.redhat.com/browse/WFCORE-5143 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 13.0.0.Beta6 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Blocker > > [~ehugonnet] please set the component. I cannot find anything suitable. > I noticed it in the context of a bootable JAR execution but [~jfdenise] confirmed this happens with WF 21 Beta1. > This is about some tests in the RESTEasy TS which has been adapted to execute against bootable JARs through a specific profile [1]. > The tests are running successfully with WildFly 20.0.1.Final (the {{ejb}} layer needs to be removed for this experiment to be run [2]) but fail against 21.0.0.Beta1, so it is a regression. > There are 108 tests failing but this JIRA is reporting just one as a reference, see "Steps to reproduce" in order to have a full list: > {code} > org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest.org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest > Error Details > Cannot deploy BlacklistedMediaTypeTest.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.BlacklistedMediaTypeTest.war\".main" => "WFLYSRV0179: Failed to load module: deployment.BlacklistedMediaTypeTest.war > Caused by: org.jboss.modules.ModuleNotFoundException: org.bouncycastle"}}}} > {code} > *Steps to reproduce*: > 1. clone https://github.com/fabiobrz/Resteasy/tree/bootable-jar-support > 2. build RESTEasy: > {code} > $ mvn install -Dmaven.test.skip=true -Dmaven.repo.local=/home/my-local-repo > {code} > 3. cd to testsuite directory: > {code} > cd testsuite > {code} > 4. run the test against WF 21.0.0.Beta1 with bootable JAR: > {code} > mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=21.0.0.Beta1 -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable > {code} > The test should *fail* > 5. run the test against WF 20.0.1.Final with bootable JAR: > {code} > mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=20.0.1.Final -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable > {code} > The test should *pass* > [1] > https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... > [2] > https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13828) remote+tls is not supported by EJBClient and remote-outbound-connection

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-13828?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty reassigned WFLY-13828: ------------------------------------------ Assignee: Ranabir Chakraborty (was: Flavia Rainone) > remote+tls is not supported by EJBClient and remote-outbound-connection > ----------------------------------------------------------------------- > > Key: WFLY-13828 > URL: https://issues.redhat.com/browse/WFLY-13828 > Project: WildFly > Issue Type: Bug > Components: Remoting > Affects Versions: 20.0.1.Final > Reporter: Matthias Großmann > Assignee: Ranabir Chakraborty > Priority: Major > > Hi, > in our company we would like to use the newest Wildfly together with legacy servers like JBoss AS 7 over SSL. > This is possible with the Uri scheme "remote+tls" provided by jboss-remoting > https://github.com/jboss-remoting/jboss-remoting/blob/master/src/main/jav... > {code:java} > final RemoteConnectionProviderFactory remoteConnectionProviderFactory = new RemoteConnectionProviderFactory(); > ... > endpoint.addConnectionProvider("remote+tls", remoteConnectionProviderFactory, OptionMap.create(Options.SECURE, Boolean.TRUE)); > {code} > But that uri scheme is not supported by the jboss-ejb-client in current version > https://github.com/wildfly/jboss-ejb-client/blob/master/src/main/java/org... > {code} > public boolean supportsProtocol(final String uriScheme) { > switch (uriScheme) { > case "remote": > case "remote+http": > case "remote+https": > // compatibility > case "remoting": > case "http-remoting": > case "https-remoting": { > return true; > } > default: { > return false; > } > } > } > {code} > and also the remote-outbound-connection does not allow that protocol: > https://github.com/wildfly/wildfly-core/blob/master/remoting/subsystem/sr... > {code} > public enum Protocol { > REMOTE("remote"), > REMOTE_HTTP("remote+http"), > HTTP_REMOTING("http-remoting"), > HTTPS_REMOTING("https-remoting"), > REMOTE_HTTPS("remote+https"); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5143) Bouncycastle - Failing tests in RESTEasy TS

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFCORE-5143?page=com.atlassian.jira.plug... ] Fabio Burzigotti commented on WFCORE-5143: ------------------------------------------ Thanks [~brian.stansberry]and [~dlofthouse] for your feedback. So IIUC this issue is still valid and to be resolved, right? > Bouncycastle - Failing tests in RESTEasy TS > ------------------------------------------- > > Key: WFCORE-5143 > URL: https://issues.redhat.com/browse/WFCORE-5143 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 13.0.0.Beta6 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Blocker > > [~ehugonnet] please set the component. I cannot find anything suitable. > I noticed it in the context of a bootable JAR execution but [~jfdenise] confirmed this happens with WF 21 Beta1. > This is about some tests in the RESTEasy TS which has been adapted to execute against bootable JARs through a specific profile [1]. > The tests are running successfully with WildFly 20.0.1.Final (the {{ejb}} layer needs to be removed for this experiment to be run [2]) but fail against 21.0.0.Beta1, so it is a regression. > There are 108 tests failing but this JIRA is reporting just one as a reference, see "Steps to reproduce" in order to have a full list: > {code} > org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest.org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest > Error Details > Cannot deploy BlacklistedMediaTypeTest.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.BlacklistedMediaTypeTest.war\".main" => "WFLYSRV0179: Failed to load module: deployment.BlacklistedMediaTypeTest.war > Caused by: org.jboss.modules.ModuleNotFoundException: org.bouncycastle"}}}} > {code} > *Steps to reproduce*: > 1. clone https://github.com/fabiobrz/Resteasy/tree/bootable-jar-support > 2. build RESTEasy: > {code} > $ mvn install -Dmaven.test.skip=true -Dmaven.repo.local=/home/my-local-repo > {code} > 3. cd to testsuite directory: > {code} > cd testsuite > {code} > 4. run the test against WF 21.0.0.Beta1 with bootable JAR: > {code} > mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=21.0.0.Beta1 -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable > {code} > The test should *fail* > 5. run the test against WF 20.0.1.Final with bootable JAR: > {code} > mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=20.0.1.Final -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable > {code} > The test should *pass* > [1] > https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... > [2] > https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13911) Intermittent deployment failures in clustering testsuite on Linux

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13911: ----------------------------------- Summary: Intermittent deployment failures in clustering testsuite on Linux Key: WFLY-13911 URL: https://issues.redhat.com/browse/WFLY-13911 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: No Release Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 21.0.0.Beta1 e.g. [https://ci.wildfly.org/buildConfiguration/WF_PullRequest_LinuxMicroProfil...] Looks to be due to a blocked thread during start of the routing registry. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13910) Class visibility problem with SimpleWebserviceEndpointTestCase with -Dts.layers

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13910: --------------------------------------- Summary: Class visibility problem with SimpleWebserviceEndpointTestCase with -Dts.layers Key: WFLY-13910 URL: https://issues.redhat.com/browse/WFLY-13910 Project: WildFly Issue Type: Bug Components: Web Services Reporter: Brian Stansberry Assignee: Jim Ma Fix For: 21.0.0.Final In recent days we've had nightly CI jobs failing with a bunch of WS failures with the first failure in SimpleWebserviceEndpointTestCase https://ci.wildfly.org/project.html?projectId=WF&testNameId=-828936378136... The failed tests in jobs that run with -Dts.layers, so the slimmed server tests. {code} org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy ws-endpoint-example.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"ws-endpoint-example.war\".POST_MODULE" => "WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"ws-endpoint-example.war\" Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class org.jboss.as.test.integration.ws.SimpleWebserviceEndpointImpl with ClassLoader ModuleClassLoader for Module \"deployment.ws-endpoint-example.war\" from Service Module Loader Caused by: java.lang.NoClassDefFoundError: Ljavax/xml/ws/WebServiceContext; Caused by: java.lang.ClassNotFoundException: javax.xml.ws.WebServiceContext from [Module \"deployment.ws-endpoint-example.war\" from Service Module Loader]"}}}} org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy ws-endpoint-example.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"ws-endpoint-example.war\".POST_MODULE" => "WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"ws-endpoint-example.war\" Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class org.jboss.as.test.integration.ws.SimpleWebserviceEndpointImpl with ClassLoader ModuleClassLoader for Module \"deployment.ws-endpoint-example.war\" from Service Module Loader Caused by: java.lang.NoClassDefFoundError: Ljavax/xml/ws/WebServiceContext; Caused by: java.lang.ClassNotFoundException: javax.xml.ws.WebServiceContext from [Module \"deployment.ws-endpoint-example.war\" from Service Module Loader]"}}}} {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4778) [DMN Designer] Multiple DRDs Support (Backlog)

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4778?page=com.atlassian.jira.plug... ] Guilherme Gomes closed DROOLS-4778. ----------------------------------- Resolution: Duplicate Issue This JIRa is being closed in favor https://issues.redhat.com/browse/KOGITO-3020. > [DMN Designer] Multiple DRDs Support (Backlog) > ---------------------------------------------- > > Key: DROOLS-4778 > URL: https://issues.redhat.com/browse/DROOLS-4778 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs related to the Multiple DRDs Support feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4779) [DMN Designer] Multiple DRDs Support - Show an interaction icon when users select more than one DMN element

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4779?page=com.atlassian.jira.plug... ] Guilherme Gomes closed DROOLS-4779. ----------------------------------- Resolution: Duplicate Issue This issue will be addressed by https://issues.redhat.com/browse/KOGITO-2673. > [DMN Designer] Multiple DRDs Support - Show an interaction icon when users select more than one DMN element > ----------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4779 > URL: https://issues.redhat.com/browse/DROOLS-4779 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: demo.gif, prototype1.png > > > When users select more than one DMN element: > !demo.gif|width=300! > We must display an interaction icon, like this one: > !prototype1.png|width=300! > ⚠️ Notice: > - The correct icon is the **sitemap** https://fontawesome.com/icons/sitemap?style=solid, https://issues.jboss.org/browse/DROOLS-3566?focusedCommentId=13804999&pag... > - We shouldn't show the icon when the selection has only one element (since we will have the **sitemap** icon for individual nodes) > - This JIRA doesn't comprehends any action. The interaction with this icon will be covered by DROOLS-4781 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4781) [DMN Designer] Multiple DRDs Support - Show DRDs action flyout menu for DRD selection

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4781?page=com.atlassian.jira.plug... ] Guilherme Gomes closed DROOLS-4781. ----------------------------------- Resolution: Duplicate Issue This issue was fixed by https://issues.redhat.com/browse/KOGITO-2664. > [DMN Designer] Multiple DRDs Support - Show DRDs action flyout menu for DRD selection > ------------------------------------------------------------------------------------- > > Key: DROOLS-4781 > URL: https://issues.redhat.com/browse/DROOLS-4781 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: prototype3.png > > > Show DRDs action flyout menu for DRD selection: > !prototype3.png|width=600! > ⚠️ Notice: > - *Before starting this JIRA*, check with [~uxdlc] which action triggers this menu (right click, single click, etc), and revisit the icons (added be DROOLS-4780 and DROOLS-4779) to add the action that will trigger this flyout menu -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4780) [DMN Designer] Multiple DRDs Support - Show a new action icon when users select one DMN element

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4780?page=com.atlassian.jira.plug... ] Guilherme Gomes closed DROOLS-4780. ----------------------------------- Resolution: Duplicate Issue This issue was fixed by https://issues.redhat.com/browse/KOGITO-2664. > [DMN Designer] Multiple DRDs Support - Show a new action icon when users select one DMN element > ----------------------------------------------------------------------------------------------- > > Key: DROOLS-4780 > URL: https://issues.redhat.com/browse/DROOLS-4780 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: prototype2.png > > > When users select one DMN element, an interaction a new action icon must be displayed: > !prototype2.png|width=600! > ⚠️ Notice: > - The correct icon is the **sitemap** https://fontawesome.com/icons/sitemap?style=solid, https://issues.jboss.org/browse/DROOLS-3566?focusedCommentId=13804999&pag... > - This JIRA doesn't comprehends any action. The interaction with this icon will be covered by DROOLS-4781 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5143) Bouncycastle - Failing tests in RESTEasy TS

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5143?page=com.atlassian.jira.plug... ] Brian Stansberry commented on WFCORE-5143: ------------------------------------------ Thanks, [~dlofthouse]. We need to be more careful when it comes to projects that base on WildFly; the meaning of 'jboss-api=private' is not clear cut at all there. Note the module isn't removed; it's just not provisioned. Sounds like it needs to be though. > Bouncycastle - Failing tests in RESTEasy TS > ------------------------------------------- > > Key: WFCORE-5143 > URL: https://issues.redhat.com/browse/WFCORE-5143 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 13.0.0.Beta6 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Blocker > > [~ehugonnet] please set the component. I cannot find anything suitable. > I noticed it in the context of a bootable JAR execution but [~jfdenise] confirmed this happens with WF 21 Beta1. > This is about some tests in the RESTEasy TS which has been adapted to execute against bootable JARs through a specific profile [1]. > The tests are running successfully with WildFly 20.0.1.Final (the {{ejb}} layer needs to be removed for this experiment to be run [2]) but fail against 21.0.0.Beta1, so it is a regression. > There are 108 tests failing but this JIRA is reporting just one as a reference, see "Steps to reproduce" in order to have a full list: > {code} > org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest.org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest > Error Details > Cannot deploy BlacklistedMediaTypeTest.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.BlacklistedMediaTypeTest.war\".main" => "WFLYSRV0179: Failed to load module: deployment.BlacklistedMediaTypeTest.war > Caused by: org.jboss.modules.ModuleNotFoundException: org.bouncycastle"}}}} > {code} > *Steps to reproduce*: > 1. clone https://github.com/fabiobrz/Resteasy/tree/bootable-jar-support > 2. build RESTEasy: > {code} > $ mvn install -Dmaven.test.skip=true -Dmaven.repo.local=/home/my-local-repo > {code} > 3. cd to testsuite directory: > {code} > cd testsuite > {code} > 4. run the test against WF 21.0.0.Beta1 with bootable JAR: > {code} > mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=21.0.0.Beta1 -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable > {code} > The test should *fail* > 5. run the test against WF 20.0.1.Final with bootable JAR: > {code} > mvn clean verify -am -pl integration-tests -Dmaven.repo.local=/home/my-local-repo -Dserver.version=20.0.1.Final -Dtest=org.jboss.resteasy.test.providers.mediatype.BlacklistedMediaTypeTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable > {code} > The test should *pass* > [1] > https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... > [2] > https://github.com/resteasy/Resteasy/pull/2526/files#diff-8c7ea03eb619e46... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

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 September 2020