[concurrency-interest] Migrating DNS problem to j.u.c
dcholmes at optusnet.com.au
Sun Dec 17 18:00:52 EST 2006
It seems your issue is with the naming service. Unless it supports some kind
of cancellation or timeout then you seem to be stuck. Sorry but I'm not
familiar with it.
> -----Original Message-----
> From: concurrency-interest-bounces at cs.oswego.edu
> [mailto:concurrency-interest-bounces at cs.oswego.edu]On Behalf Of robert
> Sent: Friday, 15 December 2006 6:53 AM
> Cc: Concurrency-interest at cs.oswego.edu
> Subject: Re: [concurrency-interest] Migrating DNS problem to j.u.c
> On 12/14/06, Joe Bowbeer <joe.bowbeer at gmail.com> wrote:
> > 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?
> What's happening AFAICT via 'netstat -ancp' is that the
> DirContext.list() sockets that were cancelled by the future get stuck
> in 'SYN_SENT' until whenever it decides to switch to 'ESTABLISHED' ,
> where it then throws 'java.net.ConnectException: Connection timed out'
> at the line of ictx.list() in the Callable inside the Runnable. Any
> idea on what I can do about that?
> > Btw, when in the timeline is ictx.close() called, and how long
> does it take
> > to complete?
> itcx.close() is called in the same finally block as exec.shutdown().
> It returns almost immediately, less than one second. I tried putting
> itcx.close() before shutdown(), to no effect.
> Thanks everyone,
> Concurrency-interest mailing list
> Concurrency-interest at altair.cs.oswego.edu
More information about the Concurrency-interest