[JBoss JIRA] (WFLY-13629) WildFly kitchensink quickstart doesn't run test when started by Maven
by Norbert Kawiński (Jira)
Norbert Kawiński created WFLY-13629:
---------------------------------------
Summary: WildFly kitchensink quickstart doesn't run test when started by Maven
Key: WFLY-13629
URL: https://issues.redhat.com/browse/WFLY-13629
Project: WildFly
Issue Type: Bug
Components: Quickstarts
Affects Versions: 20.0.0.Final
Reporter: Norbert Kawiński
Assignee: Eduardo Martins
Problem:
When running tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run.
Cause:
{color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests.
Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...]
{color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color}
* {color:#505f79}_{{**/Test*.java}}_{color}
* {color:#505f79}_{{**/*Test.java}}_{color}
* {color:#505f79}_{{**/*Tests.java}}_{color}
* {color:#505f79}{{_**/*TestCase.java_}}{color}
{color:#172b4d}{{}}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention.
{color}
{color:#172b4d}Solution:{{}}{color}
{color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (WFLY-13628) Invalidation caches need to consider keys in the cache store when reassigning ownership
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-13628:
-----------------------------------
Summary: Invalidation caches need to consider keys in the cache store when reassigning ownership
Key: WFLY-13628
URL: https://issues.redhat.com/browse/WFLY-13628
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 20.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
On cache topology changes, the distributed web/SFSB manager iterates over keys in memory to determine primary ownership changes. This is not sufficient for invalidation caches - which will not necessary contain those keys in memory that require rescheduling.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (WFLY-13627) Distributed sessions stored in non-transactional invalidation-cache should schedule expirations locally
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-13627:
-----------------------------------
Summary: Distributed sessions stored in non-transactional invalidation-cache should schedule expirations locally
Key: WFLY-13627
URL: https://issues.redhat.com/browse/WFLY-13627
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 20.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Currently, distributed web sessions (and SFSBs) are expired on the primary owner of the session. For non-transactional invalidation caches expiration should always be scheduled locally. This used to be the case, however, the logic for determining this has changed such that expirations happen on the owner of segment 0.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (WFLY-13626) Transaction subsystem CMR configuration defines optional attributes but they are handled as required
by Ondrej Chaloupka (Jira)
[ https://issues.redhat.com/browse/WFLY-13626?page=com.atlassian.jira.plugi... ]
Ondrej Chaloupka updated WFLY-13626:
------------------------------------
Description:
The {{subsystem=transactions/commit-markable-resource=...}} defines the three attributes (https://github.com/wildfly/wildfly/blob/20.0.0.Final/transactions/src/mai...) and all of them are defined as {{optional}}. But when the server is configured only with some of them it fails with
{code}
16:56:57,894 ERROR [org.jboss.as.controller] (Controller Boot Thread)
OPVDX001: Validation error in standalone.xml -----------------------------------
|
| 476: <commit-markable-resources>
| 477: <commit-markable-resource jndi-name="java:jboss/datasources/ExampleDS">
| 478: <xid-location batch-size="30" immediate-cleanup="false"/>
| ^^^^ 'xid-location' is missing one or more required attributes
|
| All of the following are required: name
|
| 479: </commit-markable-resource>
| 480: </commit-markable-resources>
| 481: </subsystem>
|
| The primary underlying error message was:
| > ParseError at [row,col]:[478,21]
| > Message: WFLYCTL0133: Missing required attribute(s): name
|
|-------------------------------------------------------------------------------
ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
at org.jboss.as.server.ServerService.boot(ServerService.java:395)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
at java.lang.Thread.run(Thread.java:748)
FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
{code}
was:
The {{subsystem=transactions/commit-markable-resource=...}} defines the three attributes (https://github.com/wildfly/wildfly/blob/20.0.0.Final/transactions/src/mai...) and all of them are defined as {{optional}}. But when the server is configured only with some of them it fails with
{quote}
16:56:57,894 ERROR [org.jboss.as.controller] (Controller Boot Thread)
OPVDX001: Validation error in standalone.xml -----------------------------------
|
| 476: <commit-markable-resources>
| 477: <commit-markable-resource jndi-name="java:jboss/datasources/ExampleDS">
| 478: <xid-location batch-size="30" immediate-cleanup="false"/>
| ^^^^ 'xid-location' is missing one or more required attributes
|
| All of the following are required: name
|
| 479: </commit-markable-resource>
| 480: </commit-markable-resources>
| 481: </subsystem>
|
| The primary underlying error message was:
| > ParseError at [row,col]:[478,21]
| > Message: WFLYCTL0133: Missing required attribute(s): name
|
|-------------------------------------------------------------------------------
ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
at org.jboss.as.server.ServerService.boot(ServerService.java:395)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
at java.lang.Thread.run(Thread.java:748)
FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
{quote}
> Transaction subsystem CMR configuration defines optional attributes but they are handled as required
> ----------------------------------------------------------------------------------------------------
>
> Key: WFLY-13626
> URL: https://issues.redhat.com/browse/WFLY-13626
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 20.0.0.Final
> Reporter: Ondrej Chaloupka
> Assignee: Ondrej Chaloupka
> Priority: Minor
>
> The {{subsystem=transactions/commit-markable-resource=...}} defines the three attributes (https://github.com/wildfly/wildfly/blob/20.0.0.Final/transactions/src/mai...) and all of them are defined as {{optional}}. But when the server is configured only with some of them it fails with
> {code}
> 16:56:57,894 ERROR [org.jboss.as.controller] (Controller Boot Thread)
> OPVDX001: Validation error in standalone.xml -----------------------------------
> |
> | 476: <commit-markable-resources>
> | 477: <commit-markable-resource jndi-name="java:jboss/datasources/ExampleDS">
> | 478: <xid-location batch-size="30" immediate-cleanup="false"/>
> | ^^^^ 'xid-location' is missing one or more required attributes
> |
> | All of the following are required: name
> |
> | 479: </commit-markable-resource>
> | 480: </commit-markable-resources>
> | 481: </subsystem>
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[478,21]
> | > Message: WFLYCTL0133: Missing required attribute(s): name
> |
> |-------------------------------------------------------------------------------
> ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
> at org.jboss.as.server.ServerService.boot(ServerService.java:395)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
> at java.lang.Thread.run(Thread.java:748)
> FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (WFLY-13626) Transaction subsystem CMR configuration defines optional attributes but they are handled as required
by Ondrej Chaloupka (Jira)
Ondrej Chaloupka created WFLY-13626:
---------------------------------------
Summary: Transaction subsystem CMR configuration defines optional attributes but they are handled as required
Key: WFLY-13626
URL: https://issues.redhat.com/browse/WFLY-13626
Project: WildFly
Issue Type: Bug
Components: Transactions
Affects Versions: 20.0.0.Final
Reporter: Ondrej Chaloupka
Assignee: Ondrej Chaloupka
The {{subsystem=transactions/commit-markable-resource=...}} defines the three attributes (https://github.com/wildfly/wildfly/blob/20.0.0.Final/transactions/src/mai...) and all of them are defined as {{optional}}. But when the server is configured only with some of them it fails with
{quote}
16:56:57,894 ERROR [org.jboss.as.controller] (Controller Boot Thread)
OPVDX001: Validation error in standalone.xml -----------------------------------
|
| 476: <commit-markable-resources>
| 477: <commit-markable-resource jndi-name="java:jboss/datasources/ExampleDS">
| 478: <xid-location batch-size="30" immediate-cleanup="false"/>
| ^^^^ 'xid-location' is missing one or more required attributes
|
| All of the following are required: name
|
| 479: </commit-markable-resource>
| 480: </commit-markable-resources>
| 481: </subsystem>
|
| The primary underlying error message was:
| > ParseError at [row,col]:[478,21]
| > Message: WFLYCTL0133: Missing required attribute(s): name
|
|-------------------------------------------------------------------------------
ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
at org.jboss.as.server.ServerService.boot(ServerService.java:395)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
at java.lang.Thread.run(Thread.java:748)
FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
{quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (JGRP-2484) SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ]
Bela Ban reopened JGRP-2484:
----------------------------
Unit tests (e.g. ASYM_ENCRYPT_TestKeyExchange) fail
> SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL
> -------------------------------------------------
>
> Key: JGRP-2484
> URL: https://issues.redhat.com/browse/JGRP-2484
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 5.0.0.Final
>
>
> WildFly OpenSSL provides a high-performance implementation of SSLContext.
> While SSL_KEY_EXCHANGE supports passing custom SSLContext instances through the programmatic API, this is not possible through the declarative API.
> It should be possible to detect the presence of WildFly OpenSSL on the classpath and use it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (SWSQE-1192) Onboar to One OCP deploy
by Filip Brychta (Jira)
Filip Brychta created SWSQE-1192:
------------------------------------
Summary: Onboar to One OCP deploy
Key: SWSQE-1192
URL: https://issues.redhat.com/browse/SWSQE-1192
Project: Kiali QE
Issue Type: Story
Reporter: Filip Brychta
{color:#000000}Onboard doc - [https://docs.google.com/document/d/1y9zEufKQt279dBFEaOIosEs860lC5KYex-Me1...
{color:#000000}One OCP Deploy is a container solution for deploying OpenShift, based on the OCP QE team’s Flexy installer. The development team’s goal is to enable 100% of all QE OCP deployment needs with this solution. It can operate both standalone and integrated in Jenkins as a node.{color}
{color:#000000}Based on multiple teams requests, the need to smoothen OCP deployment and most importantly help everyone to save time and get some reliability for deployment QE leadership asked that ALL QE teams use One OCP Deploy to deploy OpenShift. The only exception is a team that uses the IPI installer directly, with no additional tooling. {color}{color:#000000}The deadline for onboarding is Oct 4, 2020. {color}{color:#000000}If you have any questions, or feel that your team should have an additional exception, please be in touch with Sim - [sim@redhat.com|mailto:sim@redhat.com].{color}
{color:#000000}One OCP Deploy is ready for GA deployment. Because the self-service documentation isn’t fully completed, the One OCP Deploy team will be happy to help teams with onboarding. We will follow the documentation during initial onboarding, and fill in anything missing so that it should be ready for self-onboarding very quickly. The onboarding documentation, including the Jira project can be found here: {color}[+https://docs.google.com/document/d/1y9zEufKQt279dBFEaOIosEs860lC5KYex-Me1BT_1pU/edit+]{color:#000000} {color}
{color:#000000}We’re also asking every team that deploys OpenShift using any method to put the details into the following spreadsheet: {color}[+https://docs.google.com/spreadsheets/d/1R6eDSywHxesaoGBrOZmzzE9s5Woe9PNtUQKDhnANOG4/edit#gid=0+]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (JGRP-2482) Check if the largest thread pool is cluster-size + delta
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2482?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2482:
--------------------------------
If a message is internal, it will be passed to the internal thread pool, otherwise to the regular thread pool. This avoids overloading the regular pool with internal messages and thus dropping regular ones.
When fibers are mainstream, we should revisit this decision and perhaps eliminate the internal thread pool altogether...
> Check if the largest thread pool is cluster-size + delta
> --------------------------------------------------------
>
> Key: JGRP-2482
> URL: https://issues.redhat.com/browse/JGRP-2482
> Project: JGroups
> Issue Type: Task
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 5.0.0.Final
>
>
> When running UPerf in a cluster of 4, we see {{thread_pool_size_largest=39}}. Verify that MaxOneThreadPerSender works as expected: the largest thread pool size should be 4+delta (timer threads, retransmission): ~6.
> It looks as if {{MPerf}} behaves (~6 threads), but {{UPerf}} doesn't: ~26 threads
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[JBoss JIRA] (DROOLS-5453) Add/Fix pmml(s) to kie-pmml-regression tests
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5453?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-5453:
-------------------------------------
Description:
Add attached pmml(s) to kie-pmml-regression-tests and verify{code}
1) it works *without* model name
2) results are equals to the jpmml evaluator ones
3) outputfields are fixed and correctly populated
Also fix/verify all tests with the indication
{code:java}
// TODO {gcardosi} TO BE FIXED WITH DROOLS-5453{code}
was:
{code:java}
Add attached pmml(s) to kie-pmml-regression-tests and verify{code}
1) it works *without* model name
2) results are equals to the jpmml evaluator ones
3) outputfields are fixed and correctly populated
Also fix/verify all tests with the indication
{code:java}
// TODO {gcardosi} TO BE FIXED WITH DROOLS-5453{code}
> Add/Fix pmml(s) to kie-pmml-regression tests
> --------------------------------------------
>
> Key: DROOLS-5453
> URL: https://issues.redhat.com/browse/DROOLS-5453
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: TrustyAI
> Attachments: LinearRegressionSampleWithTransformations.pmml, LogisticRegression.pmml, order-approval.pmml
>
>
> Add attached pmml(s) to kie-pmml-regression-tests and verify{code}
> 1) it works *without* model name
> 2) results are equals to the jpmml evaluator ones
> 3) outputfields are fixed and correctly populated
> Also fix/verify all tests with the indication
>
> {code:java}
> // TODO {gcardosi} TO BE FIXED WITH DROOLS-5453{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months