[
https://issues.jboss.org/browse/ISPN-838?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-838:
---------------------------------------
Hmm, there's a reason why StateRetrievalType.fetchInMemoryState is set to false by
default. If you configure a cache for distribution by default state transfer would be
enabled, even if stateRetrieval element is not present, which is an invalid configuration.
You'd need to explicitly set to false in XML or programmatic configuration.
It's probably best left as is after making a note wrt to this default.
Also, all these *Type instance properties in Configuration and GlobalConfiguration are
initialized to new instances. So, if these were null by default and only instantiated when
they're configured, this type of issue would be avoided and fetchInMemoryState could
indeed be true. Maybe something for Vladimir to investigate further.
Default for fetchInMemoryState should be true
---------------------------------------------
Key: ISPN-838
URL:
https://issues.jboss.org/browse/ISPN-838
Project: Infinispan
Issue Type: Task
Components: Configuration, State transfer
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.0.0.BETA1, 5.0.0.Final
Currently the default for stateRetrieval.fetchInMemoryState is false, which means if
someone writes:
<stateRetrieval />
Then fetchInMemoryState is false, so no state transfer will occur. Instead, the default
should be switched to true, cos it's the essence of state transfer.
Otherwise, users are forced to write:
<stateRetrieval fetchInMemoryState="true" />
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira