On 14/02/2015 19:41, Mark Thomas wrote: > The proposed Apache Tomcat 8.0.19 release is now available for voting. > > The main changes since 8.0.18 are: > - Fix a performance regression in the new resources implementation > when signed JARs are used in a web application. > - Fix several bugs that could cause multiple registrations for write > events for a single socket when using Servlet 3.0 async. Typically, > the side effects of these multiple registrations would be > exceptions appearing in the logs. > - Enhance the bean factory used for JNDI resources. The new > attribute forceString allows to support non-standard string > argument property setters. > > There is also the usual collection of bug fixes, new features and > performance improvements. For full details, see the changelog: > http://svn.us.apache.org/repos/asf/tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.0.19/ > The Maven staging repo is: > https://repository.apache.org/content/repositories/orgapachetomcat-1035/ > The svn tag is: > http://svn.apache.org/repos/asf/tomcat/tc8.0.x/tags/TOMCAT_8_0_19/ > > The proposed 8.0.19 release is: > [X] Broken - do not release > [ ] Stable - go ahead and release as 8.0.19
Unit tests pass for BIO, NIO, NIO2 and APR/native on 64-bit Linux and Windows. Unit tests pass for BIO, NIO and APR/native on 64-bit OSX. Unit tests fail (2 runs in a row) for NIO2 on 64-bit OSX. The odd things is that these tests were passed at r1659807 and the only change since then were to the changelog and the build script. I suspect the pass at r1659807 was just good luck. I think I have found the root cause of the problem but I want to do a couple of test runs make sure before tagging 8.0.20. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
