[jboss-jira] [JBoss JIRA] (WFLY-9562) Issue creating replicated cache in standalone-ha
Paul Ferraro (JIRA)
issues at jboss.org
Tue Nov 21 10:21:00 EST 2017
[ https://issues.jboss.org/browse/WFLY-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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.
> Issue creating replicated cache in standalone-ha
> ------------------------------------------------
>
> Key: WFLY-9562
> URL: https://issues.jboss.org/browse/WFLY-9562
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.Final
> Reporter: Steven Hawkins
> Assignee: Paul Ferraro
>
> Attempting to install teiid into standalone-ha via a cli scripts fails with:
> {code}
> 09:12:37,399 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.clustering.infinispan.cache-configuration.teiid-cache.resultset-repl: org.jboss.msc.service.StartException in service org.wildfly.clustering.infinispan.cache-configuration.teiid-cache.resultset-repl: Failed to start service
> ...
> Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000343: Must have a transport set in the global configuration in order to define a clustered cache
> at org.infinispan.configuration.cache.ConfigurationBuilder.validate(ConfigurationBuilder.java:229)
> at org.infinispan.configuration.cache.ConfigurationBuilder.build(ConfigurationBuilder.java:240)
> at org.infinispan.configuration.ConfigurationManager.putConfiguration(ConfigurationManager.java:80)
> at org.infinispan.manager.DefaultCacheManager.defineConfiguration(DefaultCacheManager.java:390)
> at org.infinispan.manager.DefaultCacheManager.defineConfiguration(DefaultCacheManager.java:353)
> at org.jboss.as.clustering.infinispan.DefaultCacheContainer.defineConfiguration(DefaultCacheContainer.java:73)
> at org.wildfly.clustering.infinispan.spi.service.ConfigurationBuilder.start(ConfigurationBuilder.java:88)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> ... 3 more
> {code}
> This worked with prior WildFly releases.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list