[JBoss JIRA] (WFLY-13855) remote-cache-container protocol-version allowed values contain last protocol version twice
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13855?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFLY-13855:
----------------------------------
Summary: remote-cache-container protocol-version allowed values contain last protocol version twice (was: remote-cache-container protocol-version allowed values contains last protocol version twice)
> remote-cache-container protocol-version allowed values contain last protocol version twice
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-13855
> URL: https://issues.redhat.com/browse/WFLY-13855
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 20.0.0.Final, 20.0.1.Final, 21.0.0.Beta1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 21.0.0.Final
>
>
> Clearly because of {{org.infinispan.client.hotrod.ProtocolVersion#PROTOCOL_VERSION_AUTO}} plus there is no pruning in place.
> Fix is to use {{org.jboss.as.clustering.controller.validation.EnumValidator#EnumValidator(java.lang.Class<E>, java.util.EnumSet<E>)}} instead.
> {code:json}
> "protocol-version" => {
> "type" => STRING,
> "description" => "This property defines the protocol version that this client should use.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => "3.0",
> "allowed" => [
> "2.0",
> "2.1",
> "2.2",
> "2.3",
> "2.4",
> "2.5",
> "2.6",
> "2.7",
> "2.8",
> "2.9",
> "3.0",
> "3.0"
> ],
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (WFLY-13855) remote-cache-container protocol-version allowed values contains last protocol version twice
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13855?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFLY-13855:
----------------------------------
Affects Version/s: 21.0.0.Beta1
> remote-cache-container protocol-version allowed values contains last protocol version twice
> -------------------------------------------------------------------------------------------
>
> Key: WFLY-13855
> URL: https://issues.redhat.com/browse/WFLY-13855
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 20.0.0.Final, 20.0.1.Final, 21.0.0.Beta1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 21.0.0.Final
>
>
> Clearly because of {{org.infinispan.client.hotrod.ProtocolVersion#PROTOCOL_VERSION_AUTO}} plus there is no pruning in place.
> Fix is to use {{org.jboss.as.clustering.controller.validation.EnumValidator#EnumValidator(java.lang.Class<E>, java.util.EnumSet<E>)}} instead.
> {code:json}
> "protocol-version" => {
> "type" => STRING,
> "description" => "This property defines the protocol version that this client should use.",
> "expressions-allowed" => true,
> "required" => false,
> "nillable" => true,
> "default" => "3.0",
> "allowed" => [
> "2.0",
> "2.1",
> "2.2",
> "2.3",
> "2.4",
> "2.5",
> "2.6",
> "2.7",
> "2.8",
> "2.9",
> "3.0",
> "3.0"
> ],
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (WFLY-13903) Bouncycastle - Failing tests in RESTEasy TS
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13903?page=com.atlassian.jira.plugi... ]
Jean Francois Denise commented on WFLY-13903:
---------------------------------------------
[~brian.stansberry], yes the mentioned failure related to galleon is: https://issues.redhat.com/browse/WFLY-13898
> Bouncycastle - Failing tests in RESTEasy TS
> -------------------------------------------
>
> Key: WFLY-13903
> URL: https://issues.redhat.com/browse/WFLY-13903
> Project: WildFly
> Issue Type: Task
> Affects Versions: 21.0.0.Beta1
> Reporter: Fabio Burzigotti
> 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, 9 months
[JBoss JIRA] (WFCORE-4674) Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path
by Francisco De Melo Junior (Jira)
[ https://issues.redhat.com/browse/WFCORE-4674?page=com.atlassian.jira.plug... ]
Francisco De Melo Junior commented on WFCORE-4674:
--------------------------------------------------
Yes [~indrajit29], just changing the `standalone.conf` is +not**+ enough to solve the issue. This RFE changed the core module as he mentioned. I added this in the case.
> Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4674
> URL: https://issues.redhat.com/browse/WFCORE-4674
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Critical
> Labels: OpenShift, jdk11
> Fix For: 13.0.0.Beta1
>
>
> If the log manager is on the boot class path with Java 11, {{-Xbootclasspath/a:jboss-logmanager.jar}}, and a custom handler, formatter or filter is used the server will fail to boot as the log manager can't see the types in jboss-modules. This seems due to the fact that the log manager is on the boot class path and jboss-modules is on the system class path.
> Example exception:
> {code}
> Failed to read or configure the org.jboss.logmanager.LogManager
> java.lang.IllegalArgumentException: Failed to load module "org.jboss.logmanager" for formatter "JSON"
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:65)
> at org.jboss.logmanager.config.FormatterConfigurationImpl.<init>(FormatterConfigurationImpl.java:30)
> at org.jboss.logmanager.config.LogContextConfigurationImpl.addFormatterConfiguration(LogContextConfigurationImpl.java:172)
> at org.jboss.logmanager.PropertyConfigurator.configureFormatter(PropertyConfigurator.java:631)
> at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:701)
> at org.jboss.logmanager.PropertyConfigurator.configureLogger(PropertyConfigurator.java:583)
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:521)
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97)
> at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:170)
> at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:132)
> at java.util.logging.LogManager$3.run(LogManager.java:399)
> at java.util.logging.LogManager$3.run(LogManager.java:396)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:396)
> at java.util.logging.LogManager.access$800(LogManager.java:145)
> at java.util.logging.LogManager$2.run(LogManager.java:345)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:338)
> at java.util.logging.LogManager.getLogManager(LogManager.java:378)
> at org.jboss.modules.Main.main(Main.java:523)
> Caused by: java.lang.NoClassDefFoundError: org/jboss/modules/ModuleLoader
> at org.jboss.logmanager.config.AbstractPropertyConfiguration$ModuleFinder.getClassLoader(AbstractPropertyConfiguration.java:556)
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:63)
> ... 19 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (WFLY-13903) Bouncycastle - Failing tests in RESTEasy TS
by Fabio Burzigotti (Jira)
[ https://issues.redhat.com/browse/WFLY-13903?page=com.atlassian.jira.plugi... ]
Fabio Burzigotti reassigned WFLY-13903:
---------------------------------------
Assignee: Emmanuel Hugonnet
> Bouncycastle - Failing tests in RESTEasy TS
> -------------------------------------------
>
> Key: WFLY-13903
> URL: https://issues.redhat.com/browse/WFLY-13903
> Project: WildFly
> Issue Type: Task
> Affects Versions: 21.0.0.Beta1
> Reporter: Fabio Burzigotti
> 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, 9 months
[JBoss JIRA] (WFLY-13903) Bouncycastle - Failing tests in RESTEasy TS
by Fabio Burzigotti (Jira)
[ https://issues.redhat.com/browse/WFLY-13903?page=com.atlassian.jira.plugi... ]
Fabio Burzigotti updated WFLY-13903:
------------------------------------
Description:
[~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...
was:
I set the component to {{Build System}} because this only happens with Bootable JAR and - as [~jdenise] noticed - it's related with Galleon.
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.
Also, the tests are passing when the TS is executed against a distributed WildFly version, and only fail when the server is packaged via the {{wildfly-jar-maven-plugin}}.
There are 108 tests failing but htis JIRA focuses on those failing because of the following error:
{code}
RESTEASY002005: Failed executing POST /all/a/z: org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find MessageBodyWriter for response object of type: org.jboss.resteasy.test.validation.resource.ValidationFoo of media type: application/xml;charset=UTF-8
{code}
hence I guess serialization issues when the request accept header is not {{application/json}}, e.g. {{org.jboss.resteasy.test.validation.ValidationTest}}
*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. run the test against WF 21.0.0.Beta1:
{code}
cd testsuite
{code}
{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.validation.ValidationTest
{code}
The test should *pass*
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.validation.ValidationTest -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.validation.ValidationTest -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...
> Bouncycastle - Failing tests in RESTEasy TS
> -------------------------------------------
>
> Key: WFLY-13903
> URL: https://issues.redhat.com/browse/WFLY-13903
> Project: WildFly
> Issue Type: Task
> Affects Versions: 21.0.0.Beta1
> Reporter: Fabio Burzigotti
> 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, 9 months
[JBoss JIRA] (WFLY-13903) Bouncycastle - Failing tests in RESTEasy TS
by Fabio Burzigotti (Jira)
[ https://issues.redhat.com/browse/WFLY-13903?page=com.atlassian.jira.plugi... ]
Fabio Burzigotti updated WFLY-13903:
------------------------------------
Component/s: (was: Build System)
> Bouncycastle - Failing tests in RESTEasy TS
> -------------------------------------------
>
> Key: WFLY-13903
> URL: https://issues.redhat.com/browse/WFLY-13903
> Project: WildFly
> Issue Type: Task
> Affects Versions: 21.0.0.Beta1
> Reporter: Fabio Burzigotti
> Priority: Blocker
>
> I set the component to {{Build System}} because this only happens with Bootable JAR and - as [~jdenise] noticed - it's related with Galleon.
> 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.
> Also, the tests are passing when the TS is executed against a distributed WildFly version, and only fail when the server is packaged via the {{wildfly-jar-maven-plugin}}.
> There are 108 tests failing but htis JIRA focuses on those failing because of the following error:
> {code}
> RESTEASY002005: Failed executing POST /all/a/z: org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find MessageBodyWriter for response object of type: org.jboss.resteasy.test.validation.resource.ValidationFoo of media type: application/xml;charset=UTF-8
> {code}
> hence I guess serialization issues when the request accept header is not {{application/json}}, e.g. {{org.jboss.resteasy.test.validation.ValidationTest}}
> *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. run the test against WF 21.0.0.Beta1:
> {code}
> cd testsuite
> {code}
> {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.validation.ValidationTest
> {code}
> The test should *pass*
> 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.validation.ValidationTest -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.validation.ValidationTest -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, 9 months
[JBoss JIRA] (WFLY-13903) Bouncycastle - Failing tests in RESTEasy TS
by Fabio Burzigotti (Jira)
Fabio Burzigotti created WFLY-13903:
---------------------------------------
Summary: Bouncycastle - Failing tests in RESTEasy TS
Key: WFLY-13903
URL: https://issues.redhat.com/browse/WFLY-13903
Project: WildFly
Issue Type: Task
Components: Build System
Affects Versions: 21.0.0.Beta1
Reporter: Fabio Burzigotti
Assignee: Jean Francois Denise
I set the component to {{Build System}} because this only happens with Bootable JAR and - as [~jdenise] noticed - it's related with Galleon.
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.
Also, the tests are passing when the TS is executed against a distributed WildFly version, and only fail when the server is packaged via the {{wildfly-jar-maven-plugin}}.
There are 108 tests failing but htis JIRA focuses on those failing because of the following error:
{code}
RESTEASY002005: Failed executing POST /all/a/z: org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find MessageBodyWriter for response object of type: org.jboss.resteasy.test.validation.resource.ValidationFoo of media type: application/xml;charset=UTF-8
{code}
hence I guess serialization issues when the request accept header is not {{application/json}}, e.g. {{org.jboss.resteasy.test.validation.ValidationTest}}
*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. run the test against WF 21.0.0.Beta1:
{code}
cd testsuite
{code}
{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.validation.ValidationTest
{code}
The test should *pass*
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.validation.ValidationTest -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.validation.ValidationTest -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, 9 months
[JBoss JIRA] (WFLY-13903) Bouncycastle - Failing tests in RESTEasy TS
by Fabio Burzigotti (Jira)
[ https://issues.redhat.com/browse/WFLY-13903?page=com.atlassian.jira.plugi... ]
Fabio Burzigotti reassigned WFLY-13903:
---------------------------------------
Assignee: (was: Jean Francois Denise)
> Bouncycastle - Failing tests in RESTEasy TS
> -------------------------------------------
>
> Key: WFLY-13903
> URL: https://issues.redhat.com/browse/WFLY-13903
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Affects Versions: 21.0.0.Beta1
> Reporter: Fabio Burzigotti
> Priority: Blocker
>
> I set the component to {{Build System}} because this only happens with Bootable JAR and - as [~jdenise] noticed - it's related with Galleon.
> 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.
> Also, the tests are passing when the TS is executed against a distributed WildFly version, and only fail when the server is packaged via the {{wildfly-jar-maven-plugin}}.
> There are 108 tests failing but htis JIRA focuses on those failing because of the following error:
> {code}
> RESTEASY002005: Failed executing POST /all/a/z: org.jboss.resteasy.core.NoMessageBodyWriterFoundFailure: Could not find MessageBodyWriter for response object of type: org.jboss.resteasy.test.validation.resource.ValidationFoo of media type: application/xml;charset=UTF-8
> {code}
> hence I guess serialization issues when the request accept header is not {{application/json}}, e.g. {{org.jboss.resteasy.test.validation.ValidationTest}}
> *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. run the test against WF 21.0.0.Beta1:
> {code}
> cd testsuite
> {code}
> {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.validation.ValidationTest
> {code}
> The test should *pass*
> 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.validation.ValidationTest -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.validation.ValidationTest -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, 9 months