W3C home > Mailing lists > Public > www-jigsaw@w3.org > March to April 1997

Killing a client HTTP connection

From: Mark Friedman <mark@intraspect.com>
Date: Mon, 17 Mar 1997 09:56:12 -0800
To: www-jigsaw@w3.org
Message-ID: <Chameleon.858622101.mark@fooshare>
Is there any way to kill an HTTP request initiated by Jigsaw via an 
HTTPManager? When I do a runRequest() on a URL which has an invalid port, the 
runRequest never returns. A debugger stacktrace looks like:

  [1] java.lang.Object.wait (Object:152)
  [2] w3c.www.protocol.http.HttpManager.waitForConnection (pc 1)
  [3] w3c.www.protocol.http.HttpBasicServer.getConnection (pc 57)
  [4] w3c.www.protocol.http.HttpBasicServer.runRequest (pc 30)
  [5] w3c.www.protocol.http.HttpManager.runRequest (pc 104)
  [6] mygetURL.run (mygetURL:104)

I can do the runRequest in a separate thread but it I can't even stop() the 
thread. Does anyone know how to deal with this? I suppose I could just ignore 
the waiting thread but I might have a lot of these bad URLs and I would like 
to avoid having these threads lying around.

-Mark
Received on Monday, 17 March 1997 13:17:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:26 GMT