[JBoss JIRA] (WFLY-13898) Bootable JAR/Galleon - HTTP 500 is returned by some RESTEasy tests
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13898?page=com.atlassian.jira.plugi... ]
Jean Francois Denise resolved WFLY-13898.
-----------------------------------------
Resolution: Done
> Bootable JAR/Galleon - HTTP 500 is returned by some RESTEasy tests
> ------------------------------------------------------------------
>
> Key: WFLY-13898
> URL: https://issues.redhat.com/browse/WFLY-13898
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Affects Versions: 21.0.0.Beta1
> Reporter: Fabio Burzigotti
> Assignee: Jean Francois Denise
> 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)
4 years, 5 months
[JBoss JIRA] (WFLY-13898) Bootable JAR/Galleon - HTTP 500 is returned by some RESTEasy tests
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13898?page=com.atlassian.jira.plugi... ]
Jean Francois Denise edited comment on WFLY-13898 at 9/28/20 6:16 AM:
----------------------------------------------------------------------
I am resolving this issue, The [https://github.com/wildfly-extras/wildfly-jar-maven-plugin/releases/tag/2... Maven plugin depends on Galleon 4.2.6.Final that contains a fix for GAL-325.
was (Author: jdenise):
I am resolving this issue, The [2.0.0.beta8 release|[https://github.com/wildfly-extras/wildfly-jar-maven-plugin/relea...] of Maven plugin depends on Galleon 4.2.6.Final that contains a fix for GAL-325.
> Bootable JAR/Galleon - HTTP 500 is returned by some RESTEasy tests
> ------------------------------------------------------------------
>
> Key: WFLY-13898
> URL: https://issues.redhat.com/browse/WFLY-13898
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Affects Versions: 21.0.0.Beta1
> Reporter: Fabio Burzigotti
> Assignee: Jean Francois Denise
> 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)
4 years, 5 months
[JBoss JIRA] (WFLY-13898) Bootable JAR/Galleon - HTTP 500 is returned by some RESTEasy tests
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13898?page=com.atlassian.jira.plugi... ]
Jean Francois Denise commented on WFLY-13898:
---------------------------------------------
I am resolving this issue, The [2.0.0.beta8 release|[https://github.com/wildfly-extras/wildfly-jar-maven-plugin/relea...] of Maven plugin depends on Galleon 4.2.6.Final that contains a fix for GAL-325.
> Bootable JAR/Galleon - HTTP 500 is returned by some RESTEasy tests
> ------------------------------------------------------------------
>
> Key: WFLY-13898
> URL: https://issues.redhat.com/browse/WFLY-13898
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Affects Versions: 21.0.0.Beta1
> Reporter: Fabio Burzigotti
> Assignee: Jean Francois Denise
> 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)
4 years, 5 months
[JBoss JIRA] (JGRP-2108) TCP_NIO2: make default
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2108?page=com.atlassian.jira.plugin... ]
Bela Ban updated JGRP-2108:
---------------------------
Fix Version/s: 5.2
(was: 5.1)
> TCP_NIO2: make default
> ----------------------
>
> Key: JGRP-2108
> URL: https://issues.redhat.com/browse/JGRP-2108
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 5.2
>
>
> This requires the following things:
> * performance of {{TCP_NIO2}} must be better than {{TCP}}
> * (possibly) use multiple selectors: each selector handles only a max number of connections; create more selectors when the number of connections per selector exceeds a certain value
> * (possibly) get rid of the reader thread and let the above selector do the read (the write is already done by the selector thread)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (DROOLS-5677) STANDARD_DRL property reactivity doesn't recognize multiple properties in an expression
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5677?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-5677:
--------------------------------------
Description:
When a constraint expression has multiple properties, standard drl (MvelConstraint.calculateMaskFromExpression()) enlists only the first property for property reactivity (e.g. 'age' in the below case) while executable model can react on both.
{noformat}
$p : Person( age > salary )
{noformat}
was:
When a constraint expression has multiple properties, standard drl (MvelConstraint) enlists only the first property for property reactivity (e.g. 'age' in the below case) while executable model can react on both.
{noformat}
$p : Person( age > salary )
{noformat}
> STANDARD_DRL property reactivity doesn't recognize multiple properties in an expression
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-5677
> URL: https://issues.redhat.com/browse/DROOLS-5677
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.43.1.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> When a constraint expression has multiple properties, standard drl (MvelConstraint.calculateMaskFromExpression()) enlists only the first property for property reactivity (e.g. 'age' in the below case) while executable model can react on both.
> {noformat}
> $p : Person( age > salary )
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (DROOLS-5677) STANDARD_DRL property reactivity doesn't recognize multiple properties in an expression
by Toshiya Kobayashi (Jira)
Toshiya Kobayashi created DROOLS-5677:
-----------------------------------------
Summary: STANDARD_DRL property reactivity doesn't recognize multiple properties in an expression
Key: DROOLS-5677
URL: https://issues.redhat.com/browse/DROOLS-5677
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.43.1.Final
Reporter: Toshiya Kobayashi
Assignee: Toshiya Kobayashi
When a constraint expression has multiple properties, standard drl (MvelConstraint) enlists only the first property for property reactivity (e.g. 'age' in the below case) while executable model can react on both.
{noformat}
$p : Person( age > salary )
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 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:
------------------------------------
Issue Type: Bug (was: Task)
> Bouncycastle - Failing tests in RESTEasy TS
> -------------------------------------------
>
> Key: WFLY-13903
> URL: https://issues.redhat.com/browse/WFLY-13903
> Project: WildFly
> Issue Type: Bug
> 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)
4 years, 5 months