-
Bug
-
Resolution: Done
-
Critical
-
19.1.0.Final
-
None
(1) WildFly pom is used instead of EAP XP one:
<groupId>org.wildfly.bom</groupId> <artifactId>wildfly-microprofile</artifactId> <version>${version.server.bom}</version> where ${version.server.bom} is the version of your JBoss EAP XP, in our case "1.0".
This is mentioned in JBEAP-19481 as well.
(2) Unsupported commands for starting and managing EAP:
mvn wildfly:run &
mvn wildfly:execute-commands -Dwildfly.commands=/extension=org.wildfly.extension.microprofile.fault-tolerance-smallrye:add
mvn wildfly:execute-commands -Dwildfly.commands=/subsystem=microprofile-fault-tolerance-smallrye:add
mvn wildfly:shutdown -Dwildfly.reload=true
(3) I think there's no need to add the subsystem if using standalone-microprofile.xml config where it is already present.
There might be additional issues I don't see because of JBEAP-19481.
- blocks
-
JBEAP-19481 Cannot start server following the instructions in microprofile-fault-tolerance QS
- Closed
- clones
-
JBEAP-19482 Issues in readme for microprofile-fault-tolerance QS
- Closed
- is cloned by
-
WFLY-13476 MP FT QS: Missing supported shared-docs sections
- Closed