Alexander, Apologies if my reply seemed rude; that wasn't my intention. I appreciate you taking the time to respond. I just wanted to make it clear to anyone else following that it wasn't “resolved”.
On Monday, August 8, 2016 at 9:07:40 PM UTC+10, Alexander Lehmann wrote: > > I am aware of that, but I cannot give any assistance about netty, I wrote > the answer in the wrong group, I am very sorry about that. Please assume > that I didn't write the answer in the first place, since I do not know what > I am talking about. > > > > On Monday, August 8, 2016 at 9:26:41 AM UTC+2, Luke Daley wrote: >> >> Just to be clear, this question isn't “resolved”. The issue I have isn't >> about the headers to send. >> >> I'd appreciate some guidance if anyone who has implemented HTTP >> connection pooling without auto read. >> >> On Wednesday, August 3, 2016 at 1:05:57 PM UTC+10, Luke Daley wrote: >>> >>> Hi, >>> >>> I'm looking for some guidance on implementing HTTP client side >>> connection pooling. I have the basics of this working, but am uncertain >>> about handling connection termination by the server while idle. >>> >>> I'm essentially using ChannelPoolMap and the default IS_ACTIVE health >>> check on acquire and release. What I'm seeing with _some_ servers is that >>> an idle connection is being reported as isActive() when acquired, but >>> immediately goes inactive after performing the first write to it (i.e. >>> effectively failing the write). >>> >>> When channels are being returned to the pool in my case, they have >>> autoRead = false. Is this what could be causing the channel to report as >>> active until there is a write? If so, why could it be only with some >>> servers? Is it better practice to enable auto read before returning a >>> channel to the pool? >>> >>> Thanks in advance, >>> >>> Luke Daley. >>> >> -- You received this message because you are subscribed to the Google Groups "Netty discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/netty/b4454015-7de4-4ce5-9a69-ea63b758b946%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
