-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
- Install wildfly in a cluster environment
- Deploy the ear on both the master and host nodes
- Bring down wildfly on master node, (wildfly on host node is still running)
- Start wildfly on master node
Have installed Wildfly, the master node, and the host node in a cluster setup.
When the master node fails, we manually stop the host node, launch Wildfly in the master node, and then restart the host node.
Nevertheless, if the host node is not stopped before starting wildfly on master node, wildfly on master node is unable to deploy the ear and gives the following error (host node is alive)
Wildfly version : 24
{"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"img-server-group" => {"host" => {"master" => {"img-server-mgroup" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" =>
{"Operation step-1" => "WFLYCTL0063: Composite operation was rolled back"}}},"slave1" => {"img-server-1" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" =>
{"Operation step-1" => "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"custom.ear\")]"}}}}}}}}}}