Re: Memory leak but only on Red Hat
Re: Memory leak but only on Red Hat
- Subject: Re: Memory leak but only on Red Hat
- From: Q <email@hidden>
- Date: Thu, 2 Dec 2010 08:59:06 +1000
On 01/12/2010, at 5:00 PM, D Tim Cummings wrote:
^^^ There's your problem. Don't use that class, it's broken. I once encountered a case where it would not work with a particular url, no matter what I did, it would always hang. If I changed the data being returned slightly it worked fine. I have not used it since. As others have suggested, use HttpClient instead.
sendRequest(WORequest request) creates a new thread to implement timeout. I was creating threads also because the sendRequest implementation of timeout wasn't working for me. I disabled my code that created threads but was still getting the OutOfMemory problem.
Start of the thread dump below. I was able to reproduce the problem by manually clicking on the refresh page button over and over again.
-- Seeya...Q
Quinton Dolan - email@hidden Gold Coast, QLD, Australia (GMT+10)
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden