W3C home > Mailing lists > Public > www-jigsaw@w3.org > January to February 2001

Re: Client Side API - HTTP Connections

From: William Wang <gotnew@yahoo.com>
Date: Fri, 2 Feb 2001 17:12:33 -0800 (PST)
Message-ID: <20010203011233.58215.qmail@web9613.mail.yahoo.com>
To: Corey Wineman <cwineman@perseus.anserwv.org>
Cc: www-jigsaw@w3.org
I had the same headache. 

So did you succeed by using URLConnection instead?

Could you please tell me how to do it if you succeeded
with URLConnection or fix the problem of the Jigsaw.

Thanks a lot!

William

--- Corey Wineman <cwineman@perseus.anserwv.org>
wrote:
> Mark,
> 
> I have tried a couple of times to use the HTTP
> client stuff from Jigsaw.
> Once about 6 months ago, and again about a week ago.
> I was trying to use
> their stuff instead of the URLConnection classes
> that come with the JDK.
> 
> I had the same problem as you. At first everything
> seemed fine, and then I
> started losing connections. I think you are right,
> Connections aren't being
> closed properly. I think the problem is somewhere in
> the getConnection()
> method in HttpBasicServer. Sometimes it will recover
> and Connections will be
> released, other times Connections are lost forever.
> 
> Did anyone send you a response? I didn't see one. If
> I have time I will try
> and fix it myself, but it looks like a threading
> problem, and threading
> problems give me headaches.
> 
> -Corey
> 
> ----- Original Message -----
> From: <mark@mindnoise.com>
> To: <www-jigsaw@w3.org>
> Sent: Wednesday, January 31, 2001 6:43 AM
> Subject: Client Side API - HTTP Connections
> 
> 
> > Hello There!
> >
> > I'm currently using the Jigsaw 2.1.2 Client side
> API. Unfortunatley
> > I'm experiencing intermittent delays in the time
> required to
> > complete requests.
> >
> > After a whole lot of 'snooping around', I've
> noticed that HTTP
> > Connection aren't been closed correctly. This is
> causing the next
> > HTTP Connection to be delayed.
> >
> > Using the client API is it possible or how do I
> force a Http
> > connection to be closed?
> >
> > Can anyone shed any light on how Jigsaw handles
> multiple requests
> > to the same host. From what I can piece together,
> an instance of
> >
> > HttpBasicServer manages a synchronous connection
> pool for a
> > particular host.
> >
> > I think that my problem is been caused because the
> connection pool
> > is full and requests are been qued until a
> connection completes or
> > times out. Unfortunately they are never been
> released to the pool
> > because they aren't closing properly.
> >
> > Or maybe I've recently been taking too many drugs,
> haven't slept
> > enough and should go home before I loose my
> mind....
> >
> > Cheers
> > Mark Katha
> >
> > FYI: I've attached my request code...
> >         HttpManager manager =
> HttpManager.getManager();
> >         Request aRequest =
> manager.createRequest();
> >         aRequest.setMethod("GET") ;
> >         aRequest.setURL(new URL(aUrl));
> >         aRequest.setHost(aHost);
> >         Reply aReply =
> manager.runRequest(aRequest);
> >
> >
> >
> >
>
--------------------------------------------------------------------
> > Mail2Web - Check your email from the web at
> > http://www.mail2web.com/ .
> >
> >
> 


__________________________________________________
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/
Received on Friday, 2 February 2001 20:12:34 GMT

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