[
https://issues.jboss.org/browse/ISPN-4104?page=com.atlassian.jira.plugin....
]
William Burns commented on ISPN-4104:
-------------------------------------
Looking closer it appears that actually ISPN 6 interface based stores work fine. However
the limitation currently is that the ConfigurationBuilder for the store must be in the
same package and have the same name with just ConfigurationBuilder appended to the end.
The class used SingleFileStore is in the org.infinispan.persistence.file package, however
SingleFileStoreConfigurationBuilder is in the org.infinispan.configuration.cache package,
which doesn't match.
RHQ server plugin: generic store cache child creation fails
-----------------------------------------------------------
Key: ISPN-4104
URL:
https://issues.jboss.org/browse/ISPN-4104
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management
Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
Reporter: Tomas Sykora
Assignee: William Burns
This issue is similar to:
https://issues.jboss.org/browse/ISPN-4103
I can see this error during server restart:
10:38:01,682 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread
Pool -- 19) JBAS014613: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "clustered"),
("distributed-cache" => "namedCache")
]) - failure description: "JBAS010292:
org.infinispan.persistence.file.SingleFileStore is not a valid cache store"
After issuing of operation this configuration fragment is added into standalone.xml
configuration file: <store name="genericStore"
class="org.infinispan.persistence.file.SingleFileStore" preload="true"
passivation="false" purge="false"/>
Child creation using not generic, but pure File Cache Store option works OK. Store is
configured and using this class: org.infinispan.persistence.file.SingleFileStore, however,
when trying to do the same using generic store creation, it fails.
See error in linked JIRA (for loader) as I suspect there is the same cause for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira