Hello Jon,
from what I notice, this is due to the fact that the entity is not
consumed. I've just reproduced it using this code:
ClientResource cr = new
ClientResource(http://www.example.com;);
for (int i = 0; i 20; i++) {
System.out.println(i);
cr.get();
Thierry,
I have come up with a fix that solves the issue for us... but I don't know if
it is the best/right solution. It doesn't seem to be the right way to handle
it.
I'm using the 2.0.11 source.
In HttpMethodCall.sendRequest(Request) I noticed that after:
this.httpResponse =
Hello Jon,
tanks for reporting this problem, I've entered an issue for that point :
https://github.com/restlet/restlet-framework-java/issues/630
Best regards,
Thierry Boileau
I'm seeing similar behavior (leaked connections), but in a different case.
In our case we get leaked connections if
I should clarify. We are using org.restlet.ext.httpclient.
In our log file, when the request is for a valid resource URI, we see log
messages that indicate the connection is being returned to the pool.
15:18:31.193 [qtp1028854205-70 - /order] DEBUG
o.a.h.i.c.t.ThreadSafeClientConnManager -
Thanks Thierry. If you suggest where to look I'm happy to see if I can fix it.
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2994322
I'm seeing similar behavior (leaked connections), but in a different case.
In our case we get leaked connections if the request throws an exception.
We noticed this in Restlet 2.0.11, and I just tried 2.0.14 and I see the same
problem.
String uri =
Yes - that works! Many thanks.
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2888171
Thanks for the response. I thought it would be something that I was not
releasing. Constructive comment: The examples don't release the resource.
I'll try your solution next week when I'm back at work.
- Jim
--
8 matches
Mail list logo
