Again apologies in advance if I've misunderstood.
You talked of a util that encapsulates three WS client stub calls (all calls
on the same HttpClient object).
This util executes in a web container thread triggered by a request to your
portal app. You want to speed up the execution of the uti
Hi
Thanks for the replys,
I could tell little more about my setup perhaps. I've got on
eConfigurationContext that is shared between the stubs, each service has one
stub "connecte" to it. Thw web app is running inside tomcat, so the util
class that is responsible for calling managing the stubs, is
>From memory (apologies in advance if this is off the mark), I think it's the
axis2 client stub that will serialize multiple calls - i.e. will finish one
request/response before beginning another. So if you want to parallelize the
calls, what's needed is multiple client stubs, and multiple threads
Here is some code we use. Basically it uses commons pooling and creates a
pool of stubs. The expensive operation of creating the axis2 configuration
etc is only done once.
It would be simple to wrap it as a proxy of your stub interface and put the
attached code in the proxy and so the implementat
Hi
One more thing I create the HttpClient object like this
MultiThreadedHttpConnectionManager conMrg = new
MultiThreadedHttpConnectionManager();
conMrg.getParams().setDefaultMaxConnectionsPerHost(10);
httpClient = new HttpClient(conMrg);
cheers, Håkon
2009/10/9 Håkon Sagehaug
