-
Bug
-
Resolution: Done
-
Blocker
-
34.0.0.Beta1
-
None
The clustered singleton messaging feature is no longer functioning as expected. After deploying a "singleton" MDB to a 2-node cluster, neither node becomes active to consume messages.
Through a commit bisect, the issue appears to have been introduced between commits fdaa375b25bd2065039849a210129251b0d1e5d6 and 1c4f7080151b03dd7f7d920321c4c5c5c284e876. However, due to build issues with intermediate commits, it is not possible to pinpoint the exact breaking change.
The most likely cause seems to be the following commit: https://github.com/wildfly/wildfly/commit/1c4f7080151b03dd7f7d920321c4c5c5c284e876
Note this issue is breaking messaging-clustering-singleton quickstart.
- is caused by
-
WFLY-19849 On-demand anonymous singleton service have no mechanism to start
- Resolved
- is related to
-
WFLY-19813 The @ClusteredSingleton MDB feature has no test coverage.
- Open