-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR7
-
None
Currently, singleton services are started on the primary node only - no service is started on the backup nodes. We can generalize this use case by building a singleton service using 2 services: one to be started on the primary node, and the other to be installed on backup nodes. When a node is elected as the primary provider, we stop the backup service, and start the primary service. Conversely, when a primary node loses a re-election, it stops its primary service and starts its backup service.
- blocks
-
JBEAP-7732 [DOC RFE] Domain Fault Tolerance
- Closed
- causes
-
JBEAP-7508 Clustered Singleton MDB does not activate
- Closed
-
WFLY-8243 Clustered Singleton MDB does not activate
- Closed
- clones
-
WFLY-6841 Singleton backup service cannot be overridden
- Closed