Note that the new RC does not fix Igor's issue. His cache is in a state where clearing it is the only way out. We are still investigating this issue, but I'm pretty confident it's not specific to the 5.2.1 release candidate. We have seen it twice now on different instances of ATS.
I will file an issue on the corruption today. But I don't think that should hold up this RC. -- Leif > On Mar 24, 2015, at 9:08 PM, Igor Galić <i.ga...@brainsware.org> wrote: > > > > this looks good, i.e.: it fixes the assert. > +1 from me. > > > > caveat: i had to wipe my cache for it to actually work :( > > > ----- On 25 Mar, 2015, at 00:45, Leif Hedstrom zw...@apache.org wrote: > >>> On Mar 23, 2015, at 8:31 PM, Leif Hedstrom <zw...@apache.org> wrote: >>> >>> Hi all, >>> >>> I've prepared a release candidate for v5.2.1, which is a bug-fix over >>> v5.2.0. >>> The following Jira’s have been addressed in this release: >> >> >> I’ve prepared a new candidate, RC1, which adds the following fix from master: >> >> *) [TS-3140] Traffic Server asserts during response redirect. >> >> >> The new release candidates are available from the same place: >> >> http://people.apache.org/~zwoop/rel-candidates/ >> >> >> -rw-r--r-- 1 zwoop zwoop 7671323 Mar 24 23:40 >> trafficserver-5.2.1-rc1.tar.bz2 >> -rw-r--r-- 1 zwoop zwoop 949 Mar 24 23:40 >> trafficserver-5.2.1-rc1.tar.bz2.asc >> -rw-r--r-- 1 zwoop zwoop 66 Mar 24 23:40 >> trafficserver-5.2.1-rc1.tar.bz2.md5 >> -rw-r--r-- 1 zwoop zwoop 74 Mar 24 23:40 >> trafficserver-5.2.1-rc1.tar.bz2.sha1 >> >> >> MD5: f8fa197db0f76a63fb6624d7facddfff >> SHA1: 5d1da8a1a97d8c8f88ab25300912eeef4cf8f5ae >> >> >> Thanks to everyone testing the RC0 so far, the vote is still open until >> Monday >> March 30th. >> >> Cheers, >> >> — Leif > > -- > Igor Galić > > Tel: +43 (0) 664 886 22 883 > Mail: i.ga...@brainsware.org > URL: http://brainsware.org/ > GPG: 8716 7A9F 989B ABD5 100F 4008 F266 55D6 2998 1641
