After running this in production for over two weeks now, I think that HTTPCORE-379 was indeed the bug that cause our initial problems. We've been running a build based on 736bb1b and haven't experienced any problems anymore since the upgrade.
Thanks for helping us in identifying the problem! Tobias 2014-09-29 12:07 GMT+02:00 Oleg Kalnichevski <[email protected]>: > On Sun, 2014-09-28 at 22:12 +0200, Tobias Bieniek wrote: >> > Truth to be told the release process here is so painful and silly that I >> > generally try to avoid cutting releases unless absolutely necessary. >> >> I've noticed that... though it kinda defeats the purpose of bugfixing >> if releases are that hard. Is that a general Apache thing or specific >> to this project? >> > > Let me just say it is a combination of several factors. And yes, it > utterly defeats the whole 'release early, release often' principle. > >> > My priority is to get client 4.4b1 and async client 4.1b1 released soon. >> > Past that I could try to put core 4.3.3 on vote. >> >> That would be great, thanks! I've built the current 4.3.x branch now >> and released it to our internal artifact server, but I'd prefer an >> official release. >> > > You can take my word I'll put HttpCore 4.3.3 on vote after > HttpAsyncClient 4.1b1 release. > > Oleg > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
