axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Mantaut <>
Subject Re: How to use application-defined thread pool
Date Mon, 16 Apr 2012 12:39:08 GMT
Hi Tim,
          We were using axis2/c in a similar way, reusing the
synchronous client to send requests... It seems to work better than
spawning one client per request, because every client must allocate
several resources (file descriptors, etc) which makes the client
           However, you must be aware there is a bug when spawning
many clients (starting more or less at a 100 clients) that makes the
client segfault, because some file openings are not being validated,
and when the file descriptors for the process saturate there is an
invalid file descriptor somewhere... For those sort of loads it is
better to implement some sort of process pool, in order to avoid the

Hope it was helpful

On Sat, Apr 14, 2012 at 12:51 PM, Tim Stowell <> wrote:
> Hi All,
> I'm currently using Axis2C with wsdl-generated stubs. At the moment I create
> a single stub/environment, then use that to make
> multiple synchronous requests one after another, while I recreate the ADB
> objects for each request but I reuse the stub. This seems to work fine (is
> it ok to reuse the same stub?)
> However to make the app more responsive, I'd like to have one or more
> threads spawned to send the syncrounous requests. If I create multiple
> stubs/environments, can I reuse each one in it's own thread to perform the
> calls, or is there a better way to do this? Thanks!

Mantaut Alex
Intraway Corp.

+54 (11) 6040-4000

Visit our website at
Proud to be an ISO 9001:2008 certified company

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message