[concurrency-interest] Migrating DNS problem to j.u.c

Joe Bowbeer joe.bowbeer at gmail.com
Thu Dec 14 13:42:56 EST 2006

Your cancellation is requesting an interrupt via cancel(true), so it seems
that ictx.list() isn't responding to the interrupt.

Can you enhance ictx.list() to quit when it is interrupted?

Btw, when in the timeline is ictx.close() called, and how long does it take
to complete?

On 12/14/06, robert lazarski <robertlazarski at gmail.com> wrote:
> Indeed, I was submitting tasks to a shutdown pool, thanks. I now have
> a latch, which seems to now know when to shutdown the pool.
> My current problem is that the future times out correctly, but
> DirContext.list() isn't being cancelled of course, as it throws
> "java.net.ConnectException: Connection timed out" long after
> Future.cancel() . Page 148 of jcip states that closing the underlying
> socket could help, but in this case I'm not sure how I could do that.
> The program calls shutdown after about 90 seconds, but hangs for 5 and
> a half more minutes. Any ideas?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/attachments/20061214/104793c3/attachment.html 

More information about the Concurrency-interest mailing list