[
https://jira.jboss.org/jira/browse/ISPN-338?page=com.atlassian.jira.plugi...
]
Galder Zamarreno updated ISPN-338:
----------------------------------
JBoss Forum Reference:
http://lists.jboss.org/pipermail/infinispan-dev/2010-January/002272.html
Description: Currently, fetchPersistentState is only enabled if
fetchInMemoryState is on, but this shouldn't be the case. fetchPersistentState on its
own is a valid configuration. (was: > > Hi,
>
> Re:
http://community.jboss.org/thread/146590
>
> "Also, if I set the fetchInMemoryState to false in <stateRetrieval />
> and fetchPersistentState to true in <loader />, the persistent state
> transfer never happens (the code [StateTransferManagerImpl.java] is
> never run through the debugger)."
>
> That's because of
>
https://anonsvn.jboss.org/repos/infinispan/trunk/core/src/main/java/org/i...
>
> if (configuration.getCacheMode().isClustered() &&
> configuration.isFetchInMemoryState())
> return componentType.cast(new StateTransferManagerImpl());
> else
> return null;
>
> Is this intended? I do not see such limitation in JBoss Cache. Fetching
> the persistent state but not the in-memory one sounds like a valid case.
Yes,
that's correct - that check would need to be updated.
)
fetchPersistentState should be allowed regardless of
fetchInMemoryState
-----------------------------------------------------------------------
Key: ISPN-338
URL:
https://jira.jboss.org/jira/browse/ISPN-338
Project: Infinispan
Issue Type: Bug
Components: Configuration, Loaders and Stores
Affects Versions: 4.0.0.CR3
Reporter: Galder Zamarreno
Assignee: Galder Zamarreno
Fix For: 4.0.0.GA
Currently, fetchPersistentState is only enabled if fetchInMemoryState is on, but this
shouldn't be the case. fetchPersistentState on its own is a valid configuration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira