On Nov 29, 9:24 pm, Samuh <[email protected]> wrote: > I should take the time out to go through the code. > > I read somewhere that if the stream is at least read in full, the > connection is returned back to the pool.
That may be the case. Of course, if you're not processing the EOF yourself, how do you know for sure? :-) > I tried making almost concurrent requests from different threads and > it seems that there is only a certain thread that is blocked waiting > for a Connection. A quick check shows that the thread tries parsing > the stream using a pull parser and returns before END_DOCUMENT is > encountered. Maybe this is causing a connection leak? A pull parser might only be reading from the stream as much as is needed to parse the next element. If it doesn't reach the end of the document, it might be the case that it's not processing the entire stream. Something as simple as trailing whitespace might also prevent a pull parser from reading the entire stream even if the entire document is processed. Again, no hard evidence here, just speculation. > Thanks again for your reply and time! Hope I've been helpful! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
