Pavel Ausianik wrote: > I get a Call from pool from thread t1. Since it is not exists, pool create > it, t1 use it, creating a DocumentBuilder, return to pool > I get a Call from pool from thread 2. Since we have an instance of Call in > pool, it will be reused. The operation is not finished yet in the thread > t2. > I get a Call from pool from thread t1. Since it is not exists, pool create > it, again from t1, since DocumentBuilder for t1 exists, it will be reused > in new Call.
Sorry but this is not a valid scenario for Apache SOAP - the Apache SOAP APIs are not thread-safe for mutlithreaded execution like this. So you cannot have a pool of threads and a pool of Call's and reuse them like this. Things could break horribly if a call object is reused while another call is in progress. If you assume that Calls are not re-used across threads then this approach works fine right? Sanjiva. -- To unsubscribe, e-mail: <mailto:soap-dev-unsubscribe@;xml.apache.org> For additional commands, e-mail: <mailto:soap-dev-help@;xml.apache.org>
