[JBoss JIRA] (WFLY-13898) Bootable JAR/Galleon - HTTP 500 is returned by some RESTEasy tests
by Fabio Burzigotti (Jira)
[ https://issues.redhat.com/browse/WFLY-13898?page=com.atlassian.jira.plugi... ]
Fabio Burzigotti commented on WFLY-13898:
-----------------------------------------
Hi [~jdenise] - I am not reproducing in QE context. Indeed I don't need #4 locally. Am I missing something?
> 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)
5 years
[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:
--------------------------------------
{noformat}
Doing this by misconfiguring an application is not the right way. Depending on the application you're running, there needs to be an option to disable clustering and run it in standalone mode. Please refer to the project/product manual how to do that. If that's RHSSO/Keycloak, please contact me by email and I should be able to help you.{noformat}
Didn't understand, is there a way to disable it?
> 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)
5 years
[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 adding the steps to reproduce outside QE context:
1)clone [https://github.com/resteasy/Resteasy/pull/2526]
2) mvn clean install -DskipTests
3) cd testsuite
4) mvn install:install-file -Dpackaging=pom -Dfile=pom.xml -DpomFile=pom.xml
5) mvn verify -Dtest=org.jboss.resteasy.test.crypto.VerifyDecryptTest -Ddisable.microprofile.tests -Dserver.home=foo -Dts.bootable -Dserver.version=21.0.0.Beta1
> 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)
5 years
[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:
---------------------------------------------
[~fburzigo], I checked the bouncycastle issue, it also fails without Bootable JAR. I suspect that it has been caused by the bouncycastle module refactoring. I replaced the dependency in crypto to org.bouncycastle (refactored to contain what it contained in WF20) and the test passes with bootable. I sent the information to [~ehugonnet] . You can log a different bug, it is not caused by galleon.
> 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)
5 years
[JBoss JIRA] (DROOLS-5676) Fix traits injection
by Luca Molteni (Jira)
Luca Molteni created DROOLS-5676:
------------------------------------
Summary: Fix traits injection
Key: DROOLS-5676
URL: https://issues.redhat.com/browse/DROOLS-5676
Project: Drools
Issue Type: Enhancement
Reporter: Luca Molteni
Assignee: Luca Molteni
Currently the traits module inject persistence, it should do that only in the test kie.conf as the src/main/resources kie.conf is shared to each project importing the drools-traits module via mave.
Also the readme that you need to import the TraitComponentFactory in the kie.conf but it's not needed, as stated above.
Remove also the TraitComponentFactory from the drools-examples
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[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:
---------------------------------------------
[~fburzigo], I am analyzing the org.bouncycastle one.
> 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)
5 years
[JBoss JIRA] (DROOLS-5375) Implement GeneratePMMLModelMojo inside kie-maven-plugin
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5375?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-5375:
-------------------------------------
Description:
GeneratePMMLModelMojo has been implemented as part of https://issues.redhat.com/browse/DROOLS-5258 and it is currently present inside
https://github.com/gitgabrio/droolsjbpm-integration/tree/DROOLS-5258 branch.
-Thing to fix:-
-currently the plugin works if the source project is correctly layed down (i.e. every pmml file in its own package and kmodule.xml manually written out).-
-A way is needed so that user put all pmml files inside resources/PMMLResources and the model is correctly compiled.-
-It is needed to have a pre-compile phase (before any compilation) where-
-1) resources are moved to expected "resource" subfolder-
-2) kmodule.xml is generated-
-This must happen before invocation of kie build.--
Fixed by DROOLS-5367
was:
GeneratePMMLModelMojo has been implemented as part of https://issues.redhat.com/browse/DROOLS-5258 and it is currently present inside
https://github.com/gitgabrio/droolsjbpm-integration/tree/DROOLS-5258 branch.
-Thing to fix:-
-currently the plugin works if the source project is correctly layed down (i.e. every pmml file in its own package and kmodule.xml manually written out).-
-A way is needed so that user put all pmml files inside resources/PMMLResources and the model is correctly compiled.-
-It is needed to have a pre-compile phase (before any compilation) where-
-1) resources are moved to expected "resource" subfolder-
-2) kmodule.xml is generated-
-This must happen before invocation of kie build.--
Fixed by DROOLS-5367
Depends on https://github.com/kiegroup/drools/pull/3117
> Implement GeneratePMMLModelMojo inside kie-maven-plugin
> --------------------------------------------------------
>
> Key: DROOLS-5375
> URL: https://issues.redhat.com/browse/DROOLS-5375
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: TrustyAI
>
> GeneratePMMLModelMojo has been implemented as part of https://issues.redhat.com/browse/DROOLS-5258 and it is currently present inside
> https://github.com/gitgabrio/droolsjbpm-integration/tree/DROOLS-5258 branch.
> -Thing to fix:-
> -currently the plugin works if the source project is correctly layed down (i.e. every pmml file in its own package and kmodule.xml manually written out).-
> -A way is needed so that user put all pmml files inside resources/PMMLResources and the model is correctly compiled.-
> -It is needed to have a pre-compile phase (before any compilation) where-
> -1) resources are moved to expected "resource" subfolder-
> -2) kmodule.xml is generated-
> -This must happen before invocation of kie build.--
> Fixed by DROOLS-5367
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years