[jboss-jira] [JBoss JIRA] (WFLY-8216) Cannot Specify Attribute 'cluster' Within The cache-container Configuration (EAP 7.0.2)

[Radoslav Husar (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-8216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar moved JBEAP-9067 to WFLY-8216:
---------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-8216  (was: JBEAP-9067)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Clustering
                           (was: Clustering)
    Affects Version/s: 10.1.0.Final
                           (was: 7.0.2.GA)


> Cannot Specify Attribute 'cluster' Within The cache-container Configuration (EAP 7.0.2)
> ---------------------------------------------------------------------------------------
>
>                 Key: WFLY-8216
>                 URL: https://issues.jboss.org/browse/WFLY-8216
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 10.1.0.Final
>         Environment: Red Hat JBoss Enterprise Application Platform 7.0.2
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>
> It seems that specifying the attribute 'cluster' within the cache-container configuration is no longer possible for EAP 7.0.2. With EAP 6.x, one could specify the 'cluster' attribute like such:
> <cache-container name="web" aliases="standard-session-cache" default-cache="repl" module="org.jboss.as.clustering.web.infinispan">
>     <transport cluster="testname" lock-timeout="60000"/>
>     <replicated-cache name="repl" mode="ASYNC" batching="true">
>            <file-store/>
>      </replicated-cache>
> </cache-container>
> Resulting in the following (log):
> INFO  [stdout] (ServerService Thread Pool -- 58) GMS: address=rhel-box/testname, cluster=testname, physical address=127.0.0.1:55200
> ...
> 16:34:40,662 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 58) ISPN000094: Received new cluster view: [rhel-box/testname|0] [rhel-box/testname]
> It seems that this functionality is no longer in EAP 7.x. Specifying the above results in parsing errors (although the attribute 'cluster' seems valid per the Infinispan xsd). 
> ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> 	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
> 	at org.jboss.as.server.ServerService.boot(ServerService.java:356)
> 	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
> 	at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[224,17]
> Message: WFLYCTL0197: Unexpected attribute 'cluster' encountered
> 	at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:117)
> 	at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseTransport(InfinispanSubsystemXMLReader.java:309)
> 	at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.parseContainer(InfinispanSubsystemXMLReader.java:183)
> 	at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.readElement(InfinispanSubsystemXMLReader.java:75)
> 	at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader.readElement(InfinispanSubsystemXMLReader.java:53)
> 	at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> 	at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
> 	at org.jboss.as.server.parsing.StandaloneXml_4.parseServerProfile(StandaloneXml_4.java:546)
> 	at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:242)
> 	at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:141)
> 	at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103)
> 	at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49)
> 	at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> 	at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
> 	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
> 	... 3 more
> This also seems to be the case for the latest EAP 7.0.4 release.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)