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

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492347#comment-13492347 ] 

Steven Hawkins commented on WFLY-9562:
--------------------------------------

> Perform all related operations for creating a cache-container or cache within a batch

That seems to work.  Thank you.

> 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.

I'll make that update as well.  Is there a deprecation message that is expected somewhere?  I did see one related to the batching attribute, but nothing on the component paths.




> 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)