Bump hazelcast from 3.2.2 to 3.11 in /java/dlockhazalel

[dependabot]

Bumps hazelcast from 3.2.2 to 3.11.

Release notes

Sourced from hazelcast's releases.

3.11

Release Notes

v3.11-BETA-1

3.11-BETA-1 release

3.10.7

This document includes the new features, enhancements and fixed issues for Hazelcast IMDG v3.10.7, Open Source edition release.

Fixes

• Fixed an issue where the Near Cache invalidation was not working properly when used with Transactional Map. #16617

3.10.6

This document includes the new features, enhancements and fixed issues for Hazelcast IMDG v3.10.6, Open Source edition release.

Enhancements

• Added the ability to log IOExceptions thrown by the ICMP ping task as ping failures. #13826

Fixes

• Entry processors equipped with predicates try to utilize global indexes to narrow down the key set to operate on. #13892 fixes the following issues for this utilization:
  • There were no migration stamp validations performed to prevent entry processors from operating on stale index data.
  • WrongTargetException was not thrown for out-migrated partitions, as a result the caller (InvokeOnPartitions) was not retrying entry processors on such partitions.
  • Partition scope provided to PartitionIteratingOperation was not respected. As a result, operations produced by factories providing their own partition sets were running on more partitions than expected.
• Fixed the incorrect dependencies in hazelcast-all.pom. #13885
• Hazelcast lacks a mechanism for the client/server recovery within Spring cache context. This is fixed by recreating the local cache configurations when the client is connecting to a restarted member. #13811
• Clients were sometimes failing to reconnect to another owner member with the ExecutionException. This is fixed by making ClientReauthOperation to be retryable. #13790
• When an unserializableResponse is tried to be sent to the client as a response from the executor service tasks, the exception was logged on the server side and there was no response returned back to the client. This has been fixed by removing the logging and sending HazelcastSerializationException to the client. #13777
• Queryable entries returned by High-Density Memory Store indexes were unaware of the map value extractors, so it was not possible to extract values provided by the extractors from the returned entries. This is fixed by forwarding the map value extractor to these indexes. #13775
• Hazelcast 3.10.5 client was not being auto-discovered on Kubernetes. This is fixed by using a specific TLS version, namely v1.2, for SSLContext. #13760
• There is a scheduled task to clean the client resources. When an endpoint is removed, this task keeps a reference to it and this was causing unnecessary leak. This is fixed by passing only the necessary field objects of the client endpoint to this task to avoid keeping reference to the client endpoint itself. #13755
• When merging MultiMap entries, MERGE events were being fired. Now they are not since MultiMap does not have a merging listener. #13714
• Fixed the heartbeat resume mechanism where the heartbeat of a connection was becoming unhealthy when the last read time is lower than the heartbeat timeout. #13684
• Added the storage.clear operation before storage.destroy to release the High-Density (HD) Memory Store resources, since using only storage.destroy releases the internal resources of backing data structure, not the HD resources. #13659
• Moved the alive check in ClientConnectionManager to a more centralized method and fixed the exception type. #13525
• Fixed an issue where a joining member was not validating the initial cluster version. #13390
• When a Near Cache is used for an IMap and a TransactionalMap is used on a client then the get(key) operation fails reporting a wrong key type. This is fixed by skipping the Near Cache lookup at the member side, for the client’s transaction request. #13371
• HDTxnSetOperation was not taking the changes made by MapInterceptor into account while sending the backups. Now it replicates the result of interceptPut. #12705

3.10.5

This document includes the new features, enhancements and fixed issues for Hazelcast IMDG v3.10.5, Open Source edition release.

Enhancements

• Introduced OperationThreadSamples as a new diagnostics plugin. It samples the operation threads and checks the running operations/tasks. See OperationThreadSamples.

Fixes

• Added a workaround for the Constructor cache, which performs caching under incorrect keys, such that you have now the option not to use that cache. #13679
• A client connection could not detect whether it has been idle and hence the member was closing the connection. This is fixed now so that the member does not close the connections when the clients only listen. #13576
• Fixed the MultiMapValue serialization error occurred when merging MultiMap entries. It was caused by firing MERGE events which expect the entry values to be serialized. Since MultiMap does not have a MERGE listener, there was no need to fire these events; this has been fixed and now no MERGE events are fired during the merging process. #13559
• When a client is waiting for a lock to be released for a period more than invocation timeout seconds and the member dies, the client was getting an operation timeout exception. This behavior is fixed so that the operation is now retried on the new member of that lock. #13551

... (truncated)

Commits

• 1500bbb Use fixed past base time for Record timestamps (#13983)
• bfe2442 Update release_notes.txt
• 68d61da Merge pull request #13972 from furkansenharputlu/3.11
• 8ee6d20 add user-lib to classpath
• 83a3765 Update changelog.txt
• 7d3c1e3 Update release_notes.txt
• 701f0b2 3.11
• e6d277b Merge pull request #13956 from ahmetmircik/fix/3.11/CacheExpirationBouncingMe...
• 99a59a1 Merge pull request #13957 from ahmetmircik/fix/3.11/checkDestroyedNC
• 1c55a2c Sent queued expired keys on commit migration step
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

[dependabot]

Superseded by #25.