-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR4
-
None
<cached-connection-manager> is enabled in jca subsystem by default:
<subsystem xmlns="urn:jboss:domain:jca:1.1"> ... <cached-connection-manager /> </subsystem>
However, it is unable to re-enable <cached-connection-manager> once it is disabled. CLI command fails to add it due to duplicate resource.
[standalone@localhost:9990 /] /subsystem=jca/cached-connection-manager=cached-connection-manager:remove { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } [standalone@localhost:9990 /] :reload { "outcome" => "success", "result" => undefined } [standalone@localhost:9990 /] /subsystem=jca/cached-connection-manager=cached-connection-manager:add { "outcome" => "failed", "failure-description" => "JBAS014803: Duplicate resource [ (\"subsystem\" => \"jca\"), (\"cached-connection-manager\" => \"cached-connection-manager\") ]", "rolled-back" => true }
- causes
-
JBEAP-8916 CachedConnectionManager add operation accepts no parameters anymore
- Closed
- clones
-
WFLY-2640 Unable to add cached-connection-manager after removing it once
- Closed