Class ReactorClientHttpRequestFactory
- All Implemented Interfaces:
Lifecycle
,Phased
,SmartLifecycle
,ClientHttpRequestFactory
- Direct Known Subclasses:
ReactorNettyClientRequestFactory
ClientHttpRequestFactory
.
This class implements SmartLifecycle
and can be optionally declared
as a Spring-managed bean in order to support JVM Checkpoint Restore.
- Since:
- 6.2
- Author:
- Arjen Poutsma, Juergen Hoeller, Sebastien Deleuze
-
Field Summary
Fields inherited from interface org.springframework.context.SmartLifecycle
DEFAULT_PHASE
-
Constructor Summary
ConstructorDescriptionConstructor with default client, created viaHttpClient.create()
, and withcompression
enabled.ReactorClientHttpRequestFactory
(ReactorResourceFactory resourceFactory, Function<reactor.netty.http.client.HttpClient, reactor.netty.http.client.HttpClient> mapper) Constructor with externally managed Reactor Netty resources, includingLoopResources
for event loop threads, andConnectionProvider
for connection pooling.ReactorClientHttpRequestFactory
(reactor.netty.http.client.HttpClient client) Constructor with a givenHttpClient
instance. -
Method Summary
Modifier and TypeMethodDescriptioncreateRequest
(URI uri, HttpMethod httpMethod) Create a newClientHttpRequest
for the specified URI and HTTP method.int
getPhase()
Return the phase that this lifecycle object is supposed to run in.boolean
Check whether this component is currently running.void
setConnectTimeout
(int connectTimeout) Set the connect timeout value on the underlying client.void
setConnectTimeout
(Duration connectTimeout) Variant ofsetConnectTimeout(int)
with aDuration
value.void
setExchangeTimeout
(long exchangeTimeout) Deprecated, for removal: This API element is subject to removal in a future version.as of 6.2 and no longer set by default (previously 5 seconds) in favor of using Reactor Netty HttpClient timeout configuration.void
setExchangeTimeout
(Duration exchangeTimeout) Deprecated, for removal: This API element is subject to removal in a future version.as of 6.2 and no longer set by default (previously 5 seconds) in favor of using Reactor Netty HttpClient timeout configuration.void
setReadTimeout
(long readTimeout) Variant ofsetReadTimeout(Duration)
with a long value.void
setReadTimeout
(Duration timeout) Set the read timeout value on the underlying client.void
start()
Start this component.void
stop()
Stop this component, typically in a synchronous fashion, such that the component is fully stopped upon return of this method.Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
Methods inherited from interface org.springframework.context.SmartLifecycle
isAutoStartup, stop
-
Constructor Details
-
ReactorClientHttpRequestFactory
public ReactorClientHttpRequestFactory()Constructor with default client, created viaHttpClient.create()
, and withcompression
enabled. -
ReactorClientHttpRequestFactory
public ReactorClientHttpRequestFactory(reactor.netty.http.client.HttpClient client) Constructor with a givenHttpClient
instance.- Parameters:
client
- the client to use
-
ReactorClientHttpRequestFactory
public ReactorClientHttpRequestFactory(ReactorResourceFactory resourceFactory, Function<reactor.netty.http.client.HttpClient, reactor.netty.http.client.HttpClient> mapper) Constructor with externally managed Reactor Netty resources, includingLoopResources
for event loop threads, andConnectionProvider
for connection pooling.Generally, it is recommended to share resources for event loop concurrency. This can be achieved either by participating in the JVM-wide, global resources held in
HttpResources
, or by using a specific, shared set of resources through aReactorResourceFactory
bean. The latter can ensure that resources are shut down when the Spring ApplicationContext is stopped/closed and restarted again (e.g. JVM checkpoint restore).- Parameters:
resourceFactory
- the resource factory to get resources frommapper
- for further initialization of the client
-
-
Method Details
-
setConnectTimeout
public void setConnectTimeout(int connectTimeout) Set the connect timeout value on the underlying client. Effectively, a shortcut forhttpClient.option(CONNECT_TIMEOUT_MILLIS, timeout)
.By default, set to 30 seconds.
- Parameters:
connectTimeout
- the timeout value in millis; use 0 to never time out.- See Also:
-
Transport.option(ChannelOption, Object)
ChannelOption.CONNECT_TIMEOUT_MILLIS
- Connection Timeout
-
setConnectTimeout
Variant ofsetConnectTimeout(int)
with aDuration
value. -
setReadTimeout
Set the read timeout value on the underlying client. Effectively, a shortcut forHttpClient.responseTimeout(Duration)
.By default, set to 10 seconds.
- Parameters:
timeout
- the read timeout value in millis; must be > 0.
-
setReadTimeout
public void setReadTimeout(long readTimeout) Variant ofsetReadTimeout(Duration)
with a long value. -
setExchangeTimeout
Deprecated, for removal: This API element is subject to removal in a future version.as of 6.2 and no longer set by default (previously 5 seconds) in favor of using Reactor Netty HttpClient timeout configuration.Set the timeout for the HTTP exchange in milliseconds.By default, as of 6.2 this is no longer set.
-
setExchangeTimeout
Deprecated, for removal: This API element is subject to removal in a future version.as of 6.2 and no longer set by default (previously 5 seconds) in favor of using Reactor Netty HttpClient timeout configuration.Variant ofsetExchangeTimeout(long)
with a Duration value.By default, as of 6.2 this is no longer set.
-
createRequest
Description copied from interface:ClientHttpRequestFactory
Create a newClientHttpRequest
for the specified URI and HTTP method.The returned request can be written to, and then executed by calling
ClientHttpRequest.execute()
.- Specified by:
createRequest
in interfaceClientHttpRequestFactory
- Parameters:
uri
- the URI to create a request forhttpMethod
- the HTTP method to execute- Returns:
- the created request
- Throws:
IOException
- in case of I/O errors
-
start
public void start()Description copied from interface:Lifecycle
Start this component.Should not throw an exception if the component is already running.
In the case of a container, this will propagate the start signal to all components that apply.
-
stop
public void stop()Description copied from interface:Lifecycle
Stop this component, typically in a synchronous fashion, such that the component is fully stopped upon return of this method. Consider implementingSmartLifecycle
and itsstop(Runnable)
variant when asynchronous stop behavior is necessary.Note that this stop notification is not guaranteed to come before destruction: On regular shutdown,
Lifecycle
beans will first receive a stop notification before the general destruction callbacks are being propagated; however, on hot refresh during a context's lifetime or on aborted refresh attempts, a given bean's destroy method will be called without any consideration of stop signals upfront.Should not throw an exception if the component is not running (not started yet).
In the case of a container, this will propagate the stop signal to all components that apply.
-
isRunning
public boolean isRunning()Description copied from interface:Lifecycle
Check whether this component is currently running.In the case of a container, this will return
true
only if all components that apply are currently running. -
getPhase
public int getPhase()Description copied from interface:SmartLifecycle
Return the phase that this lifecycle object is supposed to run in.The default implementation returns
SmartLifecycle.DEFAULT_PHASE
in order to letstop()
callbacks execute before regularLifecycle
implementations.- Specified by:
getPhase
in interfacePhased
- Specified by:
getPhase
in interfaceSmartLifecycle
- See Also:
-