]
Ryan Emerson commented on ISPN-7644:
------------------------------------
[~rmacor] The Asynch cache loader options shouldn't be explicitly be exposed to the
user like they currently are. I will remove them from the dropdown.
I was unable to reproduce your problem with "Single File Store". If I define the
loader as a "Single File Store" on the default config, but I don't specify a
store, then upon restart the loader is still defined as expected.
Administration console - loader tab allows to set invalid options
-----------------------------------------------------------------
Key: ISPN-7644
URL:
https://issues.jboss.org/browse/ISPN-7644
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management
Affects Versions: 9.0.0.CR2
Reporter: Roman Macor
Assignee: Ryan Emerson
Click on cache container -> cache -> configuration -> loader tab
Some options in loader type drop down such as "Async Cache loader" (but there
might be more of them) result in following error, after cluster restart:
ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 19)
WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datagrid-infinispan"),
("cache-container" => "clustered"),
("configurations" => "CONFIGURATIONS"),
("distributed-cache-configuration" => "distributedCache")
]) - failure description: "DGISPN0102:
org.infinispan.persistence.async.AsyncCacheLoader is not a valid cache store"
Then there are valid options such as "Single File Store" which work if there is
a corresponding cache store set up, in this case, File store. But if there isn't a
cache store configured, the cache is no longer available after restart and configuration
cannot be fixed from the console.
I suggest we add a restriction when configuring cache loaders in the console which
wouldn't allow the users to configure cache loader without having to configure
appropriate cache store first.