axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <>
Subject Re: Adding a ThreadPoolExecutor to transports base
Date Wed, 19 Jan 2011 12:28:15 GMT
I didn't have time to review the change, but it is causing a build
failure because LinkedBlockingDeque is only available in Java 6.


On Mon, Jan 17, 2011 at 07:40, Supun Kamburugamuva <> wrote:
> I would like to add a new thread pool executor to the transport base.
> This executor behavior is similar to java ThreadPoolExecutor except
> there is an additional parameter called waterMark.
> Here is how it is intended to work.
> Assume we are submitting requests at a rate that the thread pool cannot handle.
> When the thread pool reaches the core thread size, the queue will be
> filled from submitted tasks up to the waterMark.
> After this the thread pool will go to max threads.
> Then again the queue will start to fill, if the queue capacity is more
> than the waterMark capacity. If the queue is bounded, the
> RejectedExecutionHandler will be called. If the queue is un-bounded
> the queue will fill up until the memory is full. This behavior is same
> as the java ThreadPoolExecutor.
> Thanks,
> Supun..
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message