sir：
in the server ,how to release the connetion ? I try to release
server.release(), howerver ,it does't work ,returning 204 status .But if I
release the request ,if the access counter not beyond the maxThreads
settings ,it will ok. Do I still release connetionion in this way?Hope to
head fr
Hi David,
Thanks for the very valuable feed-back. Here are the changes that I just
made to SVN trunk:
- Fixed Javadocs of ClientResource#release() and Message#release()
- Request and responses now call their release() method upon garbage
collection. It releases any associated entity
Hi Jerome-
(comments inline)
On Sun, Jul 18, 2010 at 10:05 AM, Jerome Louvel
wrote:
> As Thierry pointed out, Representation#release() will
> close the stream immediately in your case.
I'm still trying to understand what the correct way is to use the
ClientResource API. The problem I described
e : David Fogel [mailto:carrotsa...@gmail.com]
Envoyé : mardi 13 juillet 2010 00:12
À : discuss@restlet.tigris.org
Objet : Re: Problem with HttpClient extension (org.restlet.ext.httpclient) and
unreleased connections during 404s
A quick follow-up:
Further testing shows this same hanging
thread
Hello David,
I've entered and issue ([1]) for that point, thanks for your report. As far as
I notice, a call to ClientResource#getResponseEntity#release helps to release
the connection.
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=
A quick follow-up:
Further testing shows this same hanging
thread/running-out-of-connections problem happens with successful
(200) GET requests, even if we call entity.exhaust() or
clientResource.release(), both of which seem like likely candidates
for successfully closing down the connections. A
Hi all-
We've started using Restlet's HttpClient extension (along with Apache
HttpClient 4.01).
We've hit what seems like a pretty big bug: when we make a client
request using the ClientResource API, if we GET a resource that does
not exist, that process seems to consume and never release an
Http
7 matches
Mail list logo
