dependabot[bot] opened a new pull request, #9:
URL: https://github.com/apache/geronimo-batchee/pull/9

   Bumps [hazelcast](https://github.com/hazelcast/hazelcast) from 3.1 to 3.11.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/hazelcast/hazelcast/releases";>hazelcast's 
releases</a>.</em></p>
   <blockquote>
   <h2>3.11</h2>
   <p><a href="https://docs.hazelcast.org/docs/rn/index.html#3-11";>Release 
Notes</a></p>
   <h2>v3.11-BETA-1</h2>
   <p>3.11-BETA-1 release</p>
   <h2>3.10.7</h2>
   <p>This document includes the new features, enhancements and fixed issues 
for <strong>Hazelcast IMDG v3.10.7</strong>, Open Source edition release.</p>
   <h1>Fixes</h1>
   <ul>
   <li>Fixed an issue where the Near Cache invalidation was not working 
properly when used with Transactional Map. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/pull/16617";>#16617</a></li>
   </ul>
   <h2>3.10.6</h2>
   <p>This document includes the new features, enhancements and fixed issues 
for Hazelcast IMDG v3.10.6, Open Source edition release.</p>
   <h1>Enhancements</h1>
   <ul>
   <li>Added the ability to log <code>IOException</code>s thrown by the ICMP 
ping task as ping failures. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13826";>#13826</a></li>
   </ul>
   <h1>Fixes</h1>
   <ul>
   <li>Entry processors equipped with predicates try to utilize global indexes 
to narrow down the key set to operate on. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13892";>#13892</a>
 fixes the following issues for this utilization:
   <ul>
   <li>There were no migration stamp validations performed to prevent entry 
processors from operating on stale index data.</li>
   <li><code>WrongTargetException</code> was not thrown for out-migrated 
partitions, as a result the caller (<code>InvokeOnPartitions</code>) was not 
retrying entry processors on such partitions.</li>
   <li>Partition scope provided to <code>PartitionIteratingOperation</code> was 
not respected. As a result, operations produced by factories providing their 
own partition sets were running on more partitions than expected.</li>
   </ul>
   </li>
   <li>Fixed the incorrect dependencies in <code>hazelcast-all.pom</code>. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13885";>#13885</a></li>
   <li>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. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13811";>#13811</a></li>
   <li>Clients were sometimes failing to reconnect to another owner member with 
the <code>ExecutionException</code>. This is fixed by making 
<code>ClientReauthOperation</code> to be retryable. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13790";>#13790</a></li>
   <li>When an <code>unserializableResponse</code> 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 
<code>HazelcastSerializationException</code> to the client. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13777";>#13777</a></li>
   <li>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. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13775";>#13775</a></li>
   <li>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 
<code>SSLContext</code>. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13760";>#13760</a></li>
   <li>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. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13755";>#13755</a></li>
   <li>When merging MultiMap entries, <code>MERGE</code> events were being 
fired. Now they are not since MultiMap does not have a merging listener. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13714";>#13714</a></li>
   <li>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. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13684";>#13684</a></li>
   <li>Added the <code>storage.clear</code> operation before 
<code>storage.destroy</code> to release the High-Density (HD) Memory Store 
resources, since using only <code>storage.destroy</code> releases the internal 
resources of backing data structure, not the HD resources. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13659";>#13659</a></li>
   <li>Moved the alive check in <code>ClientConnectionManager</code> to a more 
centralized method and fixed the exception type. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13525";>#13525</a></li>
   <li>Fixed an issue where a joining member was not validating the initial 
cluster version. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13390";>#13390</a></li>
   <li>When a Near Cache is used for an IMap and a TransactionalMap is used on 
a client then the <code>get(key)</code> 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. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13371";>#13371</a></li>
   <li><code>HDTxnSetOperation</code> was not taking the changes made by 
MapInterceptor into account while sending the backups. Now it replicates the 
result of <code>interceptPut</code>. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/12705";>#12705</a></li>
   </ul>
   <h2>3.10.5</h2>
   <p>This document includes the new features, enhancements and fixed issues 
for Hazelcast IMDG v3.10.5, Open Source edition release.</p>
   <h1>Enhancements</h1>
   <ul>
   <li>Introduced OperationThreadSamples as a new diagnostics plugin. It 
samples the operation threads and checks the running operations/tasks. See <a 
href="http://docs.hazelcast.org/docs/3.10.5/manual/html-single/#operationthreadsamples";>OperationThreadSamples</a>.</li>
   </ul>
   <h1>Fixes</h1>
   <ul>
   <li>Added a workaround for the <code>Constructor cache</code>, which 
performs caching under incorrect keys, such that you have now the option not to 
use that cache. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13679";>#13679</a></li>
   <li>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. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13576";>#13576</a></li>
   <li>Fixed the <code>MultiMapValue</code> 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. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13559";>#13559</a></li>
   <li>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. <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13551";>#13551</a></li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/hazelcast/hazelcast/commit/1500bbb788833a0da8cdeb50026d4774d1b44d15";><code>1500bbb</code></a>
 Use fixed past base time for Record timestamps (<a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13983";>#13983</a>)</li>
   <li><a 
href="https://github.com/hazelcast/hazelcast/commit/bfe2442b36705be8686cb2d50268376b05c8cdea";><code>bfe2442</code></a>
 Update release_notes.txt</li>
   <li><a 
href="https://github.com/hazelcast/hazelcast/commit/68d61dad81f273b267725f11d5415276cb6781fd";><code>68d61da</code></a>
 Merge pull request <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13972";>#13972</a>
 from furkansenharputlu/3.11</li>
   <li><a 
href="https://github.com/hazelcast/hazelcast/commit/8ee6d20c9551ed443e10dc859f151afe9da8a4b2";><code>8ee6d20</code></a>
 add user-lib to classpath</li>
   <li><a 
href="https://github.com/hazelcast/hazelcast/commit/83a37656aa2c4d1214a29335265ecc4dab236114";><code>83a3765</code></a>
 Update changelog.txt</li>
   <li><a 
href="https://github.com/hazelcast/hazelcast/commit/7d3c1e385e8fa24831fbc25776370970107ffc40";><code>7d3c1e3</code></a>
 Update release_notes.txt</li>
   <li><a 
href="https://github.com/hazelcast/hazelcast/commit/701f0b2f8231833dd954f34b7ba9de442cc91d3d";><code>701f0b2</code></a>
 3.11</li>
   <li><a 
href="https://github.com/hazelcast/hazelcast/commit/e6d277bc700a67f71986a1394369aee64fb370af";><code>e6d277b</code></a>
 Merge pull request <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13956";>#13956</a>
 from ahmetmircik/fix/3.11/CacheExpirationBouncingMe...</li>
   <li><a 
href="https://github.com/hazelcast/hazelcast/commit/99a59a1475b21a65a75ce1a1bc4cdfa1f746ce09";><code>99a59a1</code></a>
 Merge pull request <a 
href="https://github-redirect.dependabot.com/hazelcast/hazelcast/issues/13957";>#13957</a>
 from ahmetmircik/fix/3.11/checkDestroyedNC</li>
   <li><a 
href="https://github.com/hazelcast/hazelcast/commit/1c55a2c3b6c573f0fb0cd1ca6e15c02d347f87e2";><code>1c55a2c</code></a>
 Sent queued expired keys on commit migration step</li>
   <li>Additional commits viewable in <a 
href="https://github.com/hazelcast/hazelcast/compare/v3.1...v3.11";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.hazelcast:hazelcast&package-manager=maven&previous-version=3.1&new-version=3.11)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   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-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   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](https://github.com/apache/geronimo-batchee/network/alerts).
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@geronimo.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to