[concurrency-interest] Callable inside a Runnable and RejectedExecutionException

Joe Bowbeer joe.bowbeer at gmail.com
Wed Dec 13 20:19:10 EST 2006

The trace indicates that the task was rejected.  This might happen if the
pool thread limit has been reached and the backing queue is full, or (I
think) if the executor has been shutdown.

Has nothing to do with the task itself.

On 12/13/06, robert lazarski <robertlazarski at gmail.com> wrote:
> This is just proof of concept code, but I'll take the suggestion.
> Here's the stack trace:
> [java] Caused by: java.util.concurrent.RejectedExecutionException
>      [java]     at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(
> ThreadPoolExecutor.java:1477)
>      [java]     at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java
> :384)
>      [java]     at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java
> :856)
>      [java]     at
> java.util.concurrent.AbstractExecutorService.submit(
> AbstractExecutorService.java:45)
>      [java]     at org.DNS$2.run(DNS.java:147)
> Where DNS.java:147 is exec.submit(listTask) . I thought it might be
> something about having Callable in a Runnable, but maybe not?
> Robert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/attachments/20061213/aefc7315/attachment.html 

More information about the Concurrency-interest mailing list