[
https://issues.jboss.org/browse/WFLY-7912?page=com.atlassian.jira.plugin....
]
Tomas Hofman commented on WFLY-7912:
------------------------------------
Right, that works, thanks for explanation.
It's not possible to change election-policy of singleton-policy
---------------------------------------------------------------
Key: WFLY-7912
URL:
https://issues.jboss.org/browse/WFLY-7912
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.1.0.Final
Reporter: Tomas Hofman
Assignee: Paul Ferraro
Attempt to change election policy:
{code}
[standalone@localhost:9990 /] batch
[standalone@localhost:9990 / #]
/subsystem=singleton/singleton-policy=default/election-policy=simple:remove
[standalone@localhost:9990 / #]
/subsystem=singleton/singleton-policy=default/election-policy=random:add
[standalone@localhost:9990 / #] run-batch
{code}
results in
{code}
The batch failed with the following error (you are remaining in the batch editing mode to
have a chance to correct the error):
WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:
Step: step-2
Operation: /subsystem=singleton/singleton-policy=default/election-policy=random:add
Failure: WFLYCTL0158: Operation handler failed:
org.jboss.msc.service.DuplicateServiceException: Service
org.wildfly.clustering.singleton.policy.default.election-policy is already registered
{code}
The bug seems to be introduced by
https://github.com/wildfly/wildfly/commit/605b22c30ae122492e7c019e330fea2...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)