Calling Different Webservices in parallel from Webapp

Question

We've got a stipes (java) web-app that needs to make about 15 different webserivce calls all from one method. For example: ...

    public Resolution userProfile()
    {
        serviceOneCall();
        serviceTwoCall();
        serviceThreeCall();
        serviceFourCall();
        ....
        serviceTenCall();

        return new RedirectResolution("profiel.jsp");
    }

All of these can be called in parallel and are not dependent on each other. The one thing that most all of these calls are doing is putting data in the session, and one or two may put data into the same object that is in the session, so thread safety is probably a concern there.

Can anyone suggest a good way of calling all of these concurrently?

Frank Pavageau · Answer 1 · 2012-09-13T20:23:40.123

5

Use an ExecutorService with a thread pool to submit Callables for each WS you need to call, and synchronize on the object which is updated when there is a chance of concurrent modification.

You may want to use Guava's concurrent extensions for an easier management of the Futures, using for example Futures.allAsList() which will convert a List<Future<T>> into a Future<List<T>>, so you only have one get() to do to wait for all the answers.

edited Sep 13 '12 at 20:23

answered Sep 13 '12 at 20:14

Frank Pavageau

11,477
1
43
53

@mattb The whole package is, actually: `ListeningExecutorService`, `ListenableFuture` & `Futures` allow you to chain asynchronous calls, have callbacks, etc. – Frank Pavageau Sep 14 '12 at 14:17

score 5 · Accepted Answer · answered Sep 13 '12 at 20:16

All solutions to doing this work in parallel is going to involve spawning new threads or submitting jobs to a thread pool for the remote network calls to happen to.

A good way to avoid thread safety problems is to use an executorService and submit subclasses of Callable<T> (to either the submit(Callable) or invokeAll(Collection<Callable>) methods) and have the Callables return the response value. This way your initial method can simply handle the return values of each call and choose to set the responses in the session or update other objects, rather than this work occurring in another thread.

So basic algorithm:

Submit each of these calls to an executorService in Callable<T> subclasses
Collect the Future<T>s you get back from the executorService
Call Future.get() on each to block until you have a response, and then process the responses however you wish back on the main thread

you still would need to synchronize on common session objects . — Geek, Sep 14 '12 at 10:09

Jason Crosby · Answer 3 · 2012-09-13T20:03:48.237

-2

for (i = 0; i <= numOfServiceCalls; i++) {
    new Thread(new Runnable() {
        switch(i) {
            case 1 : serviceOneCall();
                     break();
            case 2 : serviceTwoCall();
                     break();
            // Keep going with as many cases as you have.
        }
    });
}

edited Sep 13 '12 at 20:03

answered Sep 13 '12 at 19:56

Jason Crosby

3,533
4
28
49

Calling Different Webservices in parallel from Webapp

3 Answers3

Linked