Jersey client services - closing resources

Question

I have a service class that has a number of methods that make REST calls to a Spring REST service. Each of the methods looks like this:

public void getUser() {

        ClientConfig config = new DefaultClientConfig();
        Client client = Client.create(config);
        WebResource service = client.resource(RESOURCE_URL);


        // Get response as String
        String response = service.path("/addUser").accept(MediaType.TEXT_PLAIN)
                .get(String.class);

        return response;
    }

The above works fine but i am slightly worried that every time the method is called, new instances of ClientConfig, Client and WebResource are created. What would the side effects be of me changing the above and making ClientConfig, Client and WebResource as class level instance variables? i.e. change to this:

ClientConfig config = new DefaultClientConfig();
Client client = Client.create(config);
WebResource service = client.resource(RESOURCE_URL);

public void getUser() {         

        // Get response as String
        String response = service.path("/addUser").accept(MediaType.TEXT_PLAIN)
                .get(String.class);

        return response;
    }

 public void getUserAccount() {         

        // Get response as String
        String response = service.path("/getUserAccount").accept(MediaType.TEXT_PLAIN)
                .get(String.class);

        return response;
    }

Is the above likely to fail if multiple users call different methods at the same time? What is the best way to structure the above?

If the Jersey client methods had close() methods, i could have left them the way they were and just close the resources inside the methods.

Answer 1

From Jersey documentation:

For Client:

Methods to create instances of WebResource are thread-safe. Methods that modify configuration and or filters are not guaranteed to be thread-safe.

The creation of a Client instance is an expensive operation and the instance may make use of and retain many resources. It is therefore recommended that a Client instance is reused for the creation of WebResource instances that require the same configuration settings

For WebResource:

Methods to create a request and return a response are thread-safe. Methods that modify filters are not guaranteed to be thread-safe

While there is no explicit concurrency documentation for ClientConfig, it's clear from its source code that its safe to use in a multithreaded environment. The Client class is also thread safe, leaving just the WebResource to consider. Based on its documentation I would dedicate a new WebResource to each thread, meaning your code should look more like this:

ClientConfig config = new DefaultClientConfig();
Client client = Client.create(config);

public void getUser() {         
    WebResource service = client.resource(RESOURCE_URL);

    // Get response as String
    String response = service
        .path("/addUser")
        .accept(MediaType.TEXT_PLAIN)
        .get(String.class);

        return response;
}