[jboss-jira] [JBoss JIRA] (WFLY-9562) Issue creating replicated cache in standalone-ha

[ https://issues.jboss.org/browse/WFLY-9562?page=com.atlassian.jira.plugin.... ] Paul Ferraro closed WFLY-9562. ------------------------------ Resolution: Rejected It has always been the expectation that the operations for creating a cache-container or cache should execute within a batch. While the script in the jira description might not have failed against a previous release, it would not have yielded the expected results without a reload of the server. If this CLI script is run against a running server, you *must* either: * Perform all related operations for creating a cache-container or cache within a batch e.g. {code} batch /subsystem=infinispan/cache-container=teiid-cache:add(default-cache=resultset) /subsystem=infinispan/cache-container=teiid-cache/transport=jgroups:add(lock-timeout=60000) /subsystem=infinispan/cache-container=teiid-cache/local-cache=resultset:add() /subsystem=infinispan/cache-container=teiid-cache/local-cache=resultset/component=locking:add(isolation=READ_COMMITTED) /subsystem=infinispan/cache-container=teiid-cache/local-cache=resultset/component=expiration:add(lifespan=7200000) /subsystem=infinispan/cache-container=teiid-cache/local-cache=resultset/component=eviction:add(max-entries=1024, strategy=LIRS) /subsystem=infinispan/cache-container=teiid-cache/local-cache=resultset/component=transaction:add(mode=NON_XA) run-batch batch /subsystem=infinispan/cache-container=teiid-cache/replicated-cache=resultset-repl:add(mode=SYNC) /subsystem=infinispan/cache-container=teiid-cache/replicated-cache=resultset-repl/component=locking:add(isolation=READ_COMMITTED) /subsystem=infinispan/cache-container=teiid-cache/replicated-cache=resultset-repl/component=expiration:add(lifespan=7200000) /subsystem=infinispan/cache-container=teiid-cache/replicated-cache=resultset-repl/component=eviction:add(max-entries=1024, strategy=LIRS) /subsystem=infinispan/cache-container=teiid-cache/replicated-cache=resultset-repl/component=transaction:add(mode=NON_XA) run-batch batch /subsystem=infinispan/cache-container=teiid-cache/local-cache=preparedplan:add() /subsystem=infinispan/cache-container=teiid-cache/local-cache=preparedplan/component=locking:add(isolation=READ_COMMITTED) /subsystem=infinispan/cache-container=teiid-cache/local-cache=preparedplan/component=expiration:add(lifespan=28800) /subsystem=infinispan/cache-container=teiid-cache/local-cache=preparedplan/component=eviction:add(max-entries=512, strategy=LIRS) /subsystem=infinispan/cache-container=teiid-cache:write-attribute(name=default-cache, value=resultset) run-batch {code} * Use the \{allow-resource-service-restart=true} operation flag to ensure all services created by the related parent operation are restarted e.g. {code} /subsystem=infinispan/cache-container=teiid-cache:add() /subsystem=infinispan/cache-container=teiid-cache/transport=jgroups:add(lock-timeout=60000)\{allow-resource-service-restart=true} /subsystem=infinispan/cache-container=teiid-cache/replicated-cache=resultset-repl:add(mode=SYNC) /subsystem=infinispan/cache-container=teiid-cache/replicated-cache=resultset-repl/component=locking:add(isolation=READ_COMMITTED)\{allow-resource-service-restart=true} /subsystem=infinispan/cache-container=teiid-cache/replicated-cache=resultset-repl/component=expiration:add(lifespan=7200000)\{allow-resource-service-restart=true} /subsystem=infinispan/cache-container=teiid-cache/replicated-cache=resultset-repl/component=eviction:add(max-entries=1024, strategy=LIRS)\{allow-resource-service-restart=true} /subsystem=infinispan/cache-container=teiid-cache/replicated-cache=resultset-repl/component=transaction:add(mode=NON_XA)\{allow-resource-service-restart=true} /subsystem=infinispan/cache-container=teiid-cache/local-cache=resultset:add() /subsystem=infinispan/cache-container=teiid-cache/local-cache=resultset/component=locking:add(isolation=READ_COMMITTED)\{allow-resource-service-restart=true} /subsystem=infinispan/cache-container=teiid-cache/local-cache=resultset/component=expiration:add(lifespan=7200000)\{allow-resource-service-restart=true} /subsystem=infinispan/cache-container=teiid-cache/local-cache=resultset/component=eviction:add(max-entries=1024, strategy=LIRS)\{allow-resource-service-restart=true} /subsystem=infinispan/cache-container=teiid-cache/local-cache=resultset/component=transaction:add(mode=NON_XA)\{allow-resource-service-restart=true} /subsystem=infinispan/cache-container=teiid-cache/local-cache=preparedplan:add() /subsystem=infinispan/cache-container=teiid-cache/local-cache=preparedplan/component=locking:add(isolation=READ_COMMITTED)\{allow-resource-service-restart=true} /subsystem=infinispan/cache-container=teiid-cache/local-cache=preparedplan/component=expiration:add(lifespan=28800)\{allow-resource-service-restart=true} /subsystem=infinispan/cache-container=teiid-cache/local-cache=preparedplan/component=eviction:add(max-entries=512, strategy=LIRS)\{allow-resource-service-restart=true} /subsystem=infinispan/cache-container=teiid-cache:write-attribute(name=default-cache, value=resultset)\{allow-resource-service-restart=true} /subsystem=infinispan/cache-container=teiid-cache:write-attribute(name=default-cache, value=resultset)\{allow-resource-service-restart=true} {code} Additionally, the CLI script at the link in the jira description relies on deprecated paths for the cache components. While this still works as of WF 11, this script should be updated as support for legacy paths will be removed in a future release. -- This message was sent by Atlassian JIRA (v7.5.0#75005)