[JBoss JIRA] (ISPN-7644) Administration console - Loader tab allows invalid configuration to be set.
3:59 a.m.
[
https://issues.jboss.org/browse/ISPN-7644?page=com.atlassian.jira.plugin....
]
Roman Macor commented on ISPN-7644:
-----------------------------------
[~ryanemerson] it seems it happens with every cache loader except for "Single files
store", I thought it was all of them.
Try setting another loader e.g. String Based JDBC Store
Server log after restart:
ERROR [org.jboss.as.clustering.infinispan] (MSC service thread 1-5) DGISPN0016: Waiting
for deployment of Custom Cache Store
(org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore) timed out. Please check
if this cache store is really present.
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start
service jboss.datagrid-infinispan.clustered.repl: org.jboss.msc.service.StartException in
service jboss.datagrid-infinispan.clustered.repl: Failed to start service
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.infinispan.commons.CacheException: Unable to invoke method public void
org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type
PersistenceManagerImpl
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:172)
at
org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869)
at
org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:635)
at
org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:624)
at
org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:549)
at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:231)
at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:803)
at
org.infinispan.cache.impl.AbstractDelegatingCache.start(AbstractDelegatingCache.java:411)
at
org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:652)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:592)
at
org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:456)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:446)
at
org.infinispan.manager.impl.AbstractDelegatingEmbeddedCacheManager.getCache(AbstractDelegatingEmbeddedCacheManager.java:139)
at org.infinispan.server.infinispan.SecurityActions$5.run(SecurityActions.java:133)
at org.infinispan.server.infinispan.SecurityActions$5.run(SecurityActions.java:130)
at org.infinispan.security.Security.doPrivileged(Security.java:76)
at
org.infinispan.server.infinispan.SecurityActions.doPrivileged(SecurityActions.java:66)
at org.infinispan.server.infinispan.SecurityActions.startCache(SecurityActions.java:138)
at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:86)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
... 3 more
Caused by: org.infinispan.commons.CacheException: Unable to start cache loaders
at
org.infinispan.persistence.manager.PersistenceManagerImpl.start(PersistenceManagerImpl.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168)
... 23 more
Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000249: The cache
loader configuration
org.jboss.as.clustering.infinispan.cs.configuration.DeployedStoreConfiguration does not
specify the loader class using @ConfigurationFor
at
org.infinispan.persistence.factory.ConfigurationForClassExtractor.getClassBasedOnConfigurationAnnotation(ConfigurationForClassExtractor.java:21)
at
org.infinispan.persistence.factory.LocalClassLoaderCacheStoreFactory.createInstance(LocalClassLoaderCacheStoreFactory.java:21)
at
org.infinispan.persistence.factory.CacheStoreFactoryRegistry.createInstance(CacheStoreFactoryRegistry.java:39)
at
org.infinispan.persistence.manager.PersistenceManagerImpl.createLoadersAndWriters(PersistenceManagerImpl.java:591)
at
org.infinispan.persistence.manager.PersistenceManagerImpl.start(PersistenceManagerImpl.java:149)
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
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)
2836
days inactive
2836
days old
infinispan-issues@lists.jboss.org
0 comments
1 participants
participants (1)
-
Roman Macor (JIRA)