[JBoss JIRA] (WFLY-12461) Can't use smallrye-health without weld extension
by Florian Sailer (Jira)
Florian Sailer created WFLY-12461:
-------------------------------------
Summary: Can't use smallrye-health without weld extension
Key: WFLY-12461
URL: https://issues.jboss.org/browse/WFLY-12461
Project: WildFly
Issue Type: Bug
Components: MP Health
Affects Versions: 17.0.1.Final
Reporter: Florian Sailer
Assignee: Jeff Mesnil
Since this commit in the smallrye implementation it was possible to use smallrye without CDI.
https://github.com/smallrye/smallrye-health/commit/a6a7812877d74d2c3f5b29...
I'm trying to migrate from Wildfly 15.0.1-Final to 17.0.1-Final, where the smallrye-health extension unfortunately needs weld to startup. It's not possbible for me to activate weld on my sever, because there are some problems using the org.apache.cxf.jaxrs framework with weld.
I am getting the following exception while starting:
14:16:04,960 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-health-smallrye' are not available:
org.wildfly.weld; There are no known registration points which can provide this capability.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
7 months, 3 weeks
[JBoss JIRA] (WFLY-13630) Scattered caches should not contain a transaction resource
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-13630:
-----------------------------------
Summary: Scattered caches should not contain a transaction resource
Key: WFLY-13630
URL: https://issues.redhat.com/browse/WFLY-13630
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 20.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
This configuration throws an error at runtime. Thus we should not registered this child resource for scattered caches, nor should such a configuration be allowed by the parser.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 3 months
[JBoss JIRA] (WFLY-13629) WildFly kitchensink quickstart doesn't run test when started by Maven
by Norbert Kawiński (Jira)
[ https://issues.redhat.com/browse/WFLY-13629?page=com.atlassian.jira.plugi... ]
Norbert Kawiński updated WFLY-13629:
------------------------------------
Description:
Problem:
When running kitchensink's 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}
was:
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}
> 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
> Priority: Major
>
> Problem:
> When running kitchensink's 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)
3 years, 3 months
[JBoss JIRA] (WFLY-13629) WildFly kitchensink quickstart doesn't run test when started by Maven
by Norbert Kawiński (Jira)
[ https://issues.redhat.com/browse/WFLY-13629?page=com.atlassian.jira.plugi... ]
Norbert Kawiński updated WFLY-13629:
------------------------------------
Description:
Problem:
When running kitchensink's 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}
was:
Problem:
When running kitchensink's 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}
> 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
> Priority: Major
>
> Problem:
> When running kitchensink's 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)
3 years, 3 months
[JBoss JIRA] (WFLY-13627) Distributed sessions/SFSBs stored in non-transactional invalidation-cache should schedule expirations locally
by Paul Ferraro (Jira)
[ https://issues.redhat.com/browse/WFLY-13627?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFLY-13627:
--------------------------------
Summary: Distributed sessions/SFSBs stored in non-transactional invalidation-cache should schedule expirations locally (was: Distributed sessions stored in non-transactional invalidation-cache should schedule expirations locally)
> Distributed sessions/SFSBs 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
> Priority: Critical
>
> 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)
3 years, 3 months
[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)
3 years, 3 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)
3 years, 3 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)
3 years, 3 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)
3 years, 3 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)
3 years, 3 months