12:41 p.m.
[
https://issues.jboss.org/browse/ISPN-7644?page=com.atlassian.jira.plugin....
]
Ryan Emerson edited comment on ISPN-7644 at 3/22/17 1:40 PM:
-------------------------------------------------------------
[~rmacor] This is actually a limitation of using the `<loader class=""/>`
syntax, which is what the loaders configuration tab exposes. It won't work properly
for any of the included cache-stores as they are not listed as a dependency in
`modules/system/layers/base/org/infinispan/main/module.xml`. File-store is the exception,
as it is included in core.
Furthermore, stores configured via <loader/> don't have additional dependencies
(e.g. JDBC datasources) loaded and the user is required to configure these properties for
a working store anyway.
Users who need to utilise one of the built in cache stores purely as a loader, should use
the "stores" tab and configure their desired store as "read-only". I
propose that we remove all of the loader options from the dropdown menu, except "No
cache loader", "Cluster Loader" and "Custom Loader".
[~vblagojevic], [~NadirX] WDYT?
was (Author: ryanemerson):
[~rmacor] This is actually a limitation of using the `<loader class=""/>`
syntax, which is what the loaders configuration tab exposes. It won't work properly
for any of the included cache-stores as they are not listed as a dependency in
`modules/system/layers/base/org/infinispan/main/module.xml`. File-store is the exception,
as it is included in core.
Furthermore, stores configured via <loader/> don't have additional dependencies
(e.g. JDBC datasources) loaded and the user is required to configure these properties for
a working store anyway.
Users who need to utilise one of the built in cache stores purely as a loader, should use
the "stores" tab and configure their desired store as "read-only". I
propose that we remove all of the loader options from the dropdown menu, except "No
cache loader", "Cluster Loader" and "Custom Loader".
[~vblagojevic][~NadirX] WDYT?
Administration console - Loader tab allows invalid configuration to
be set.
---------------------------------------------------------------------------
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
Fix For: 9.0.0.Final
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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)