On Mon, Nov 25, 2019 at 12:30 PM Mark Thomas <ma...@apache.org> wrote:
> On 25/11/2019 10:44, Mark Thomas wrote: > > On 22/11/2019 20:14, Konstantin Kolinko wrote: > >> пт, 22 нояб. 2019 г. в 16:19, Violeta Georgieva <violet...@apache.org>: > >>> > >>> The proposed Apache Tomcat 7.0.98 release is now available for voting. > >>> > >>> It can be obtained from: > >>> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.98/ > >>> The Maven staging repo is: > >>> > https://repository.apache.org/content/repositories/orgapachetomcat-1239/ > >>> The git tag is: > >>> https://github.com/apache/tomcat/tree/7.0.98 > >>> fde40d7e0c7a1b0b2423cb84ad220a5d98b65591 > >>> > >>> The proposed 7.0.98 release is: > >>> [x] Broken - do not release > >>> [ ] Stable - go ahead and release as 7.0.98 Stable > >> > >> Unfortunately, it is broken. > >> Testing on Windows 10, > >> the test "org.apache.catalina.core.TestAsyncContextStateChanges" > >> always hangs for an APR connector, regardless of version of Java > >> - tested 32-bit native with 32-bit Oracle Java 6u45, 7u80 > >> - tested 64-bit native with 64-bit Java 8u222 from AdoptOpenJDK, Java > >> 13 from OpenJDK. > >> > >> For NIO and BIO connectors the same test completes successfully in 13 > seconds. > >> > >> It appears to be the same issue as was filed earlier today by Michael > >> who was testing on FreeBSD, > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=63950 > > > > I'm starting to dig into this. At the moment, my investigation is > > focussed on the APR Poller. > > Found it. It is a bug in the unit test. The client is closing the > connection too soon. I'm not sure why we are seeing this on a subset of > operating systems and a subset of versions but I'll get it fixed generally. > > It would seem the 7.0.98 build got dropped a bit too early then, can it be brought back ? Rémy
