]
Michal Karm Babacek closed WFLY-5539.
-------------------------------------
Resolution: Rejected
[~pferraro] Thanks for the hint, Paul. I'll try to programatically tinker with
Infinispan subsystem caches defined in {{standalone-ha.xml}} from within the runtime of my
deployment.
I'm closing this Issue and I'll move to the user forum with any further inquires.
Infinispan subsystem attributes are not persisted
-------------------------------------------------
Key: WFLY-5539
URL:
https://issues.jboss.org/browse/WFLY-5539
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.0.0.CR2
Reporter: Michal Karm Babacek
Assignee: Paul Ferraro
Priority: Critical
Fix For: 10.0.0.CR4
Certain cache configuration attributes are not persisted after reload. I find this issue
being a critical one because if effectively prevents me from enabling indexing on my
custom caches.
For instance, there are no attributes *indexing* nor *batching* in the
[
jboss-as-infinispan_4_0.xsd|https://github.com/wildfly/wildfly/blob/maste...],
whereas CLI allows one to set these; nonetheless in vain, because the values are not
persisted.
{noformat}
[standalone@localhost:9990 /]
/subsystem=infinispan/cache-container=server/replicated-cache=BLACKLIST_CACHE:read-attribute(name=batching)
{
"outcome" => "success",
"result" => false
}
[standalone@localhost:9990 /]
/subsystem=infinispan/cache-container=server/replicated-cache=BLACKLIST_CACHE:read-attribute(name=indexing)
{
"outcome" => "success",
"result" => "NONE"
}
[standalone@localhost:9990 /]
/subsystem=infinispan/cache-container=server/replicated-cache=BLACKLIST_CACHE:write-attribute(name=indexing,value=ALL)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[standalone@localhost:9990 /]
/subsystem=infinispan/cache-container=server/replicated-cache=BLACKLIST_CACHE:write-attribute(name=batching,value=true)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
[standalone@localhost:9990 /] reload
[standalone@localhost:9990 /]
/subsystem=infinispan/cache-container=server/replicated-cache=BLACKLIST_CACHE:read-attribute(name=indexing)
{
"outcome" => "success",
"result" => "NONE"
}
[standalone@localhost:9990 /]
/subsystem=infinispan/cache-container=server/replicated-cache=BLACKLIST_CACHE:read-attribute(name=batching)
{
"outcome" => "success",
"result" => false
}
{noformat}
Is there any other way how one could enable indexing on one's cache? E.g. my cache:
{code}
<replicated-cache name="BLACKLIST_CACHE" mode="ASYNC">
<locking acquire-timeout="60000" concurrency-level="3000"
isolation="REPEATABLE_READ"/>
<transaction mode="NONE"/>
<eviction max-entries="10000000" strategy="NONE"/>
<expiration interval="-1" lifespan="-1"
max-idle="-1"/>
<file-store/>
<state-transfer timeout="300000"/>
</replicated-cache>
{code} Obviously, adding aforementioned attributes to the cache element results in an XML
parsing error...
Last but not least, is there any way how to circumvent the bug and force indexing so as
to avoid deadly exceptions such as: {noformat}java.lang.IllegalArgumentException: Indexing
was not enabled on this cache. interface org.hibernate.search.spi.SearchIntegrator not
found in registry{noformat}? I'm very well aware of the possibility to configure the
whole cache programatically in runtime using CacheManager -- but that is the very
situation I was trying to migrate away from.
Thx for comments.