-
Bug
-
Resolution: Done
-
Major
-
10.0.0.Final
-
None
EJB3SubsystemAdd adds capability org.wildfly.ejb3.clustered.singleton but then EJB3SubsystemRemove does not remove it.
This breaks use cases where the subsystem is repeatedly added, particularly a cycle of
/profile=foo:clone(to-profile=bar)
... make some adjustments to bar
... oops, screwed up on those adjustments, lets start over!
/profile=bar:remove
/profile=foo:clone(to-profile=bar)
The last step will fail with:
[Host Controller] [33m[0m[31m12:05:13,818 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("add") failed - address: ([[0m [Host Controller] [31m ("profile" => "clone"),[0m [Host Controller] [31m ("subsystem" => "ejb3")[0m [Host Controller] [31m]): java.lang.IllegalStateException: WFLYCTL0363: Capability 'org.wildfly.ejb3.clustered.singleton' is already registered in context 'profile=clone'.[0m [Host Controller] [31m at org.jboss.as.controller.CapabilityRegistry.registerCapability(CapabilityRegistry.java:146)[0m [Host Controller] [31m at org.jboss.as.controller.OperationContextImpl.registerCapability(OperationContextImpl.java:1430)[0m [Host Controller] [31m at org.jboss.as.controller.OperationContextImpl.registerCapability(OperationContextImpl.java:1417)[0m [Host Controller] [31m at org.jboss.as.ejb3.subsystem.EJB3SubsystemAdd.recordCapabilitiesAndRequirements(EJB3SubsystemAdd.java:178)[0m