CODEWITHSUNDEEP
clientjax-rscxf
Prasad A
Prasad A

Reputation: 31

Jax rs client pool

I am working on setting up a REST Client using jax-rs 2 client API. In the api doc it says "Clients are heavy-weight objects that manage the client-side communication infrastructure. Initialization as well as disposal of a Client instance may be a rather expensive operation. It is therefore advised to construct only a small number of Client instances in the application." (https://docs.oracle.com/javaee/7/api/javax/ws/rs/client/Client.html). As per this statement it sounds like Client is not thread-safe and i should not be using single Client instance for all requests.

I am using CXF implementation, so far i didn't find a way to set up pool for Client objects.

If anyone has any information reg this could you please share.

Thanks in advance.

Upvotes: 3

Views: 6689

Answers (1)

pedrofb
pedrofb

Reputation: 39241

By default, CXF uses a transport based on the in-JDK HttpURLConnection object to perform HTTP requests.

Connection pooling is performed allowing persistent connections to reuse the underlying socket connection for multiple http requests.

Set these system properties to configure the pool(default values)

http.keepalive=true
http.maxConnections=5

Increment the value of http.maxConnections to set the maximum number of idle connections that will be simultaneously kept alive, per destination. See in this link the complete list of properties properties.html

In this post are explained some detail how it works

Java HttpURLConnection and pooling

Note also that the default JAX-RS client is not thread-safe by default. Check the limitations for proper use here

When you need many requests executed simultaneosly CXF can also use the asynchronous apache HttpAsyncClient. Ser details here

http://cxf.apache.org/docs/asynchronous-client-http-transport.html

Upvotes: 1

Related Questions