A mode attribute (SYNC/ASYNC) for caching strategy can not be modified from EAP 7.2

Solution Verified - Updated -

Issue

  • When set a mode attribute of distributed/replicated-cache like as follows, EAP doesn't start with the following validation ERROR.
<distributed-cache name="dist" mode="SYNC" />
ERROR [org.jboss.as.controller] (Controller Boot Thread) 
OPVDX001: Validation error in standalone-ha.xml --------------------------------
|
|  350: </replicated-cache>
|  351: <replicated-cache name="routing"/>
|  352: <distributed-cache name="dist" mode="SYNC">
|                                      ^^^^ 'mode' isn't an allowed attribute for the 'distributed-cache' element
|                                           
|                                           Attributes allowed here are: 
|                                             capacity-factor           owners                    
|                                             consistent-hash-strategy  remote-timeout            
|                                             l1-lifespan               segments                  
|
|  353:     <locking isolation="REPEATABLE_READ"/>
|  354:     <transaction mode="BATCH"/>
|  355:     <file-store/>
|
| 'mode' is allowed on elements: 
| - server > profile > {urn:jboss:domain:infinispan:8.0}subsystem > cache-container > local-cache > transaction
| - server > profile > {urn:jboss:domain:infinispan:8.0}subsystem > remote-cache-container > transaction
|
|
| The primary underlying error message was:
| > ParseError at [row,col]:[352,17]
| > Message: WFLYCTL0197: Unexpected attribute 'mode' encountered
|
|-------------------------------------------------------------------------------

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content