Description of problem: When defining a custom cache loader via configuration file, JBoss Data Grid (JDG) fails to boot due to parsing errors (child elements of <loader>). Looking at org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemXMLReader_5_2#parseCustomLoader, it seems that there is not support for child elements for <loader>. Version-Release number of selected component (if applicable): JBoss Data Grid 6.1 (based on Infinispan 5.2) How reproducible: Easily Steps to Reproduce: 1). Define a cache with a customer loader like such: <local-cache name="AppProps" start="EAGER"> <transaction mode="NONE"/> <loader class="com.ferguson.xp.SimpleCacheLoader"> <property name="p1">v1</property> </loader> </local-cache> Actual results: JDG fails to boot with XML parsing errors: 14:33:18,864 ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration ... Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[116,27] Message: JBAS014789: Unexpected element '{urn:infinispan:server:core:5.2}property' encountered at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:85) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4] ... Expected results: JDG can sucessfully parse elements and boot up cleanly Additional info:
Works in 6.2.0.DR1 (fixed by https://github.com/infinispan/infinispan-server/commit/e9691aa1d4eb6ac67aadea23d7912002974eb24f + new test in our testsuite).
Fixed the doc text by changing "store" to "loader". (The configuration did already work for a cache store, it was missing for a cache loader).
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.