[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)
4 years, 5 months
[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)
4 years, 5 months
[JBoss JIRA] (WFCORE-5143) Bouncycastle - Failing tests in RESTEasy TS
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-5143?page=com.atlassian.jira.plug... ]
Darran Lofthouse commented on WFCORE-5143:
------------------------------------------
FYI KeyCloak has a direct dependency on org.bouncycastle from their adaptor feature pack so we should be cautious about removing this module.
> 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)
4 years, 5 months
[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:
------------------------------------------
[~ehugonnet] [~fburzigo] [~rsigal] [~asoldano]
Note that this relies on unsupported behavior:
https://github.com/resteasy/Resteasy/blob/master/testsuite/integration-te...
The org.bouncycastle module is private and we can remove it at any time. We shouldn't in a micro release but can in a major/minor. I don't think we are obligated to provision it in a slimmed server.
If we can provision it without doing things that are too ugly, that might be fine, but this test app should package bouncycastle itself if it needs it.
> 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)
4 years, 5 months
[JBoss JIRA] (JGRP-2502) If the KUBERNETES_NAMESPACE is not set the default value is the "default" namespace
by Sebastian Laskawiec (Jira)
[ https://issues.redhat.com/browse/JGRP-2502?page=com.atlassian.jira.plugin... ]
Sebastian Laskawiec commented on JGRP-2502:
-------------------------------------------
[~filippe.spolti] oooh, I'm not a maintainer of OpenShift PING. Please reach out the maintainers of that project and ask them directly.
> If the KUBERNETES_NAMESPACE is not set the default value is the "default" namespace
> ------------------------------------------------------------------------------------
>
> Key: JGRP-2502
> URL: https://issues.redhat.com/browse/JGRP-2502
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 5.0.4
> Reporter: Filippe Spolti
> Assignee: Sebastian Laskawiec
> Priority: Minor
>
> If no namespace is set it defaults to the "default" ocp namespace which will case the warn as described in the log message below:
>
> {code:java}
> WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-9,ee,hdm78-kieserver-1-nggcf) failed getting JSON response from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:937#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.jgroups.protocols.kubernetes.stream.TokenStreamProvider@69991c01] for cluster [ee], namespace [default], labels [null]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/default/pods]]
> {code}
> IMHO the default namespace should not be used in this case since this namespace should not be used to deploy applications.
>
> If the namespace is not set it means that we do not want to enable the clustering feature, as the namespace is set if the namespace is not set, this condition [1] is not satisfied and the configuration will proceed.
>
> Another problem found in the tests is that, if we do set the KUBERNETES_NAMESPACE with no value, it will detect that the env has an value and will try to use a blank namespace:
>
> {code:java}
> failed getting JSON response from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1 , headers={Authorization=#MASKED:874#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.jgroups.protocols.kubernetes.stream.TokenStreamProvider@17978314] for cluster [ee], namespace [], labels [null]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/pods ]]
> {code}
>
> [1] - https://github.com/jgroups-extras/jgroups-kubernetes/blob/master/src/main/java/org/jgroups/protocols/kubernetes/KUBE_PING.java#L145
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (JGRP-2502) If the KUBERNETES_NAMESPACE is not set the default value is the "default" namespace
by Filippe Spolti (Jira)
[ https://issues.redhat.com/browse/JGRP-2502?page=com.atlassian.jira.plugin... ]
Filippe Spolti commented on JGRP-2502:
--------------------------------------
no asking about keycloak, just asking to have the same behavior than openshift.PING where we could disable clustering if no envs set.
> If the KUBERNETES_NAMESPACE is not set the default value is the "default" namespace
> ------------------------------------------------------------------------------------
>
> Key: JGRP-2502
> URL: https://issues.redhat.com/browse/JGRP-2502
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 5.0.4
> Reporter: Filippe Spolti
> Assignee: Sebastian Laskawiec
> Priority: Minor
>
> If no namespace is set it defaults to the "default" ocp namespace which will case the warn as described in the log message below:
>
> {code:java}
> WARN [org.jgroups.protocols.kubernetes.KUBE_PING] (thread-9,ee,hdm78-kieserver-1-nggcf) failed getting JSON response from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:937#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.jgroups.protocols.kubernetes.stream.TokenStreamProvider@69991c01] for cluster [ee], namespace [default], labels [null]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/default/pods]]
> {code}
> IMHO the default namespace should not be used in this case since this namespace should not be used to deploy applications.
>
> If the namespace is not set it means that we do not want to enable the clustering feature, as the namespace is set if the namespace is not set, this condition [1] is not satisfied and the configuration will proceed.
>
> Another problem found in the tests is that, if we do set the KUBERNETES_NAMESPACE with no value, it will detect that the env has an value and will try to use a blank namespace:
>
> {code:java}
> failed getting JSON response from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1 , headers={Authorization=#MASKED:874#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.jgroups.protocols.kubernetes.stream.TokenStreamProvider@17978314] for cluster [ee], namespace [], labels [null]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/pods ]]
> {code}
>
> [1] - https://github.com/jgroups-extras/jgroups-kubernetes/blob/master/src/main/java/org/jgroups/protocols/kubernetes/KUBE_PING.java#L145
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months