[
https://issues.jboss.org/browse/ISPN-1876?page=com.atlassian.jira.plugin....
]
Israel Lacerra edited comment on ISPN-1876 at 3/29/13 4:38 PM:
---------------------------------------------------------------
We do not have one CommandInitializer per Cache. So, the field CommandInitializer.cache
initialized in LifecyleManager.cacheStarted is confusing the distributed queries....
I'll try to do it in another way.
--EDIT--
I will put a EmbeddedCacheManager in CommandInitializer... this solves the problem.
was (Author: israeldl):
We do not have one CommandInitializer per Cache. So, the field
CommandInitializer.cache initialized in LifecyleManager.cacheStarted is confusing the
distributed queries....
I'll try to do it in another way.
clustered query is not executed on the right cache
--------------------------------------------------
Key: ISPN-1876
URL:
https://issues.jboss.org/browse/ISPN-1876
Project: Infinispan
Issue Type: Bug
Components: Querying, RPC
Affects Versions: 5.1.1.FINAL
Reporter: Mathieu Lachance
Assignee: Israel Lacerra
when using clustered query, command is not executed on the right cache.
when debuging, in CommandAwareRpcDispatcher::executeCommand()
cmd = ClusteredQuery{cache="the-good-cache-name"}
cmd.cache = "the-bad-cache-name"
cmd.cacheName = "the-good-cache-name"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira