You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to create and resume from a checkpoint using CRaC it is required that all sockets are closed before taking the snapshot. HttpAsyncClientBuilder used by the RestClientBuilder allows to set a NHttpClientConnectionManager which id defaulted to a PoolingNHttpClientConnectionManager. The pool will keep connections open for a given timeout which leads to an error when invoking jcmd ... JDK.checkpoint.
However, NHttpClientConnectionManager would allow to explicitly closeExpiredConnections() as well as closeIdleConnections which will make sure the requirements for capturing a snapshot are met.
Is there a way to provide an API on RestClient that would allow to evict open connections?
In doing so existing references to the RestClient instances will remain valid, which would not be the case if the client was closed before the checkpoint and recreated from captured settings in the afterRestore method.
The text was updated successfully, but these errors were encountered:
Description
In order to create and resume from a checkpoint using CRaC it is required that all sockets are closed before taking the snapshot.
HttpAsyncClientBuilder
used by theRestClientBuilder
allows to set aNHttpClientConnectionManager
which id defaulted to aPoolingNHttpClientConnectionManager
. The pool will keep connections open for a given timeout which leads to an error when invokingjcmd ... JDK.checkpoint
.However,
NHttpClientConnectionManager
would allow to explicitlycloseExpiredConnections()
as well ascloseIdleConnections
which will make sure the requirements for capturing a snapshot are met.Is there a way to provide an API on
RestClient
that would allow to evict open connections?In doing so existing references to the
RestClient
instances will remain valid, which would not be the case if the client was closed before the checkpoint and recreated from captured settings in the afterRestore method.The text was updated successfully, but these errors were encountered: