[concurrency-interest] Callable inside a Runnable andRejectedExecutionException

David Holmes dcholmes at optusnet.com.au
Wed Dec 13 20:37:10 EST 2006

Right. Based on Robert's other thread it appears he is shutting down the
pool while it is still in use.

  -----Original Message-----
  From: concurrency-interest-bounces at cs.oswego.edu
[mailto:concurrency-interest-bounces at cs.oswego.edu]On Behalf Of Joe Bowbeer
  Sent: Thursday, 14 December 2006 11:19 AM
  To: Concurrency-interest at cs.oswego.edu
  Subject: Re: [concurrency-interest] Callable inside a Runnable

  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]     at

         [java]     at
         [java]     at

         [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?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/attachments/20061214/3d6f5817/attachment.html 

More information about the Concurrency-interest mailing list