This section lists issues solved for Hazelcast 3.4 release.
BackupPutOperationdoes not trigger the eviction [#4297].
replaceare broken with the sync listener. The missing completion event, if the condition fails for these methods, should be added [#4251].
BINARYmode is not working. The problem seems to be in the
ClientExecutorServiceSubmitTest.javais compiled using the Eclipse compiler, it gives a compile error: "The method submit(Runnable, ExecutionCallback) is ambiguous for the type IExecutorService". The reason is that the
IExecutorService.javaclass does not have some generics. The issue has been solved by adding these missing generics to the
clearmethod should be removed that runs when the size is smaller than the minimum eviction element count (
get(key)does not count as an access to the underlying IMap. The near cache has its own
max-idle-secondselement. However, if an entry is expired/evicted in the IMap, it also causes a near cache removal operation for the entry regardless of the
max-idle-secondsof that entry in the near cache. The entry expires and is evicted even if the near cache is being hit constantly. When a near cache is hit, the underlying map should reset the idle time for that key [#4016].
checkFullyProcessedof MapReduce throws null pointer exception. The reason may be that multiple threads attempt to start the final processing state in the JobSupervisor [#3952].
RejectedExecutionExceptionis thrown [#3669].
TransactionalMap, read-only operations such as
containsValue()break the transaction atomicity [#3191].