3.5 Fixes
This section lists issues solved for Hazelcast 3.5 release.
putTransient
actuated the MapStore unexpectedly in an environment with multiple instances [#5225].removeAttribute
will prevent any updates by the method setAttribute
in the deferred write mode [#5186].CacheEvictionConfig
class was renamed to EvictionConfig
for general usage [#5180]./etc/hosts
and the members are configured manually with IP addresses and while one node is running, a second node joins to the cluster 5 minutes after it started [#5072].SlowOperationDTO.operation
shows only the class name, not the package. This can lead to ambiguity and the actual class cannot be tracked [#5041].MessageListener
interface of ITopic [#5019].InvocationFuture.isDone
returns true
as soon as there is a response including WAIT_RESPONSE
. However, WAIT_RESPONSE
is an intermediate response, not a final one [#5002].InvocationFuture.andThen
does not deal with the null response correctly [#5001].CacheCreationTest
fails due to the multiple TestHazelcastInstanceFactory
creations in the same test [#4987].putIfAbsent
method is thrown [#4981].connectionAttemptLimit
property which internally results in int.maxValue
. However, the XSD of the Hazelcast Spring configuration requires it to be at least 1 [#4967].hazelcastmq.txn-topic
[#4790].XmlConfigImportVariableReplacementTest
fails [#4758].size()
method for a replicated map should return 0
when the entry is removed [#4666].FinalizeJoinOperation
times out if the method MapStore.loadAllKeys()
takes more than 5
seconds [#4348].read()
forever [#3401].