No need to apologize, I certainly appreciate your responses! To answer your question, no, I don't call NHttpClientConnection#suspendInput in my code prior to putting the connection on my re-use queue.
As a possibly irrelevant point, my code functions on my Linux server if I circumvent my connection recycler but of course I'd rather not do that :-). Under Windows, the connection recycling seems to work just find and I get no errors. Does the fact that tcpdump doesn't report any outgoing message for the request that fails give me any clues as to what is happening? I'll have to take a look at the logging pointers you sent me. Peter On Tue, Sep 22, 2009 at 5:06 PM, Oleg Kalnichevski <[email protected]> wrote: > Peter Soles wrote: > >> Thanks for the response and the pointers to your code. I'll definitely >> take >> a look! >> >> I'm not clearing the read event notifications in the persistent >> connection. >> In my code, the connection is "born" when I get it from I >> NHttpClientHandler.connected() and I just place it on my re-use queue at >> the >> end of HttpRequestExecutionHandler.handleResponse(). When I need to >> re-use, >> I just check NHttpClientConnection.getStatus == ACTIVE and >> NHttpClientConnection.isOpen() == true. >> >> Should I be calling NHttpClientConnection.resetOutput()/resetInput() >> before >> I try and re-use the connection? >> >> thanks again! >> >> Peter >> >> > Sorry for not being specific enough. Do you call > NHttpClientConnection#suspendInput() anywhere in your code prior to putting > the connection on the re-use queue? > > > Oleg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
