[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1004) Lifecycle manager for plugin module is invoked twice per cache initialization on cacheStarting
[
https://issues.jboss.org/browse/ISPN-1004?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-1004:
----------------------------------------
There're two paths leading to this:
{code} at $Proxy12.cacheStarting(Unknown Source)
at
org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:191)
at org.infinispan.factories.InternalCacheFactory.bootstrap(InternalCacheFactory.java:95)
at
org.infinispan.factories.InternalCacheFactory.createAndWire(InternalCacheFactory.java:79)
at
org.infinispan.factories.InternalCacheFactory.createCache(InternalCacheFactory.java:63)
at
org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:545){code}
And:
{code} at $Proxy12.cacheStarting(Unknown Source)
at
org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:191)
at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:177)
at org.infinispan.CacheDelegate.start(CacheDelegate.java:362)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:552)
{code}
At first glance, one of those is redundant... I'll check which.
Lifecycle manager for plugin module is invoked twice per cache
initialization on cacheStarting
----------------------------------------------------------------------------------------------
Key: ISPN-1004
URL: https://issues.jboss.org/browse/ISPN-1004
Project: Infinispan
Issue Type: Bug
Components: Core API, Querying
Reporter: Sanne Grinovero
Assignee: Galder Zamarreño
Fix For: 5.0.0.CR4
In the search module the org.infinispan.query.impl.LifecycleManager is registered via the
infinispan-module.properties, but the method
{code}org.infinispan.query.impl.LifecycleManager.cacheStarting(ComponentRegistry,
Configuration, String){code}
Is invoked twice for each cache initialization.
The implementation needs to register an interceptor, and some objects in the
componentregistry. The tricky part is that some of these components are overwritten, some
are not, leading to an inconsistent initialization (Query was made useless).
I'm working around this in Query to register my needed components only if they're
not already, but this is inconsistent as well as I might need to reconfigure it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira