Am 27.03.2015 um 13:36 schrieb Violeta Georgieva:
The proposed Apache Tomcat 7.0.61 release is now available for voting.
It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.61/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1041/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_61/
The proposed 7.0.61 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 7.0.61 Stable
+1 to release, thanks for RM.
Details:
- MD5 OK
- signatures OK
- key in KEYS file
- gz and zip for src and bin consistent
- src completely consistent with svn tag
- builds fine
- warnings about unchecked calls or conversions in:
- o.a.t.dbcp
- javax/el/ResourceBundleELResolver.java
Both not a regression
- build result looks consistent with binaries
- no checkstyle complaints
- no Javadoc warnings
- Unit tests: no errors or failures
- Details of log output see below
- JMX MBean Comparison (relative 7.0.59):
- jstl.jar and standard.jar renamed to
taglibs-standard-impl-1.2.5.jar and
taglibs-standard-spec-1.2.5.jar
- tldScanTime for examples down from 603 to 242
Not sure whether that's relevant or expected or just
varying test conditions
- new attribute tomcatAutorization wth value "false" in
the ProtocolHandler MBean for port=8009
- new attribute allowedTrailerHeaders with empty value
in the ProtocolHandler MBean for port=8080.
Empty value should be OK, because by default there are
probably no allowed trailers.
- new attribute useServerCipherSuitesOrder with empty values
in the ThreadPool MBeans for 8009 and 8080
Empty value should be OK, because default value is empty string
and everything except "true" and "yes" works like false.
- OperatingSystem MBean OpenFileDescriptorCount down from 58 to 57
But this value is often changing a little, maybe due to
whether Finalizers have run or not.
Build and tests were done using Java 1.6.0_45, java.7.home was pointing
to 1.7.0_76. OS was Solaris 10 Sparc, tcnative was 1.1.32 (!) based on
APR 1.5.1 and OpenSSL 1.0.1m.
Unit test warnings
==================
117 (7.0.57: 92, 7.0.59: 141)
The change in numbers is mostly due to varying number of messages during
tribes tests, not due to completely new or gone warning messages.
Unit test SEVERE messages
=========================
544 (7.0.57: 548, 7.0.59: 554)
The change in numbers is mostly due to varying number of messages during
tribes tests and of type WebappClassLoader.clearReferencesThreads (The
web application ... appears to have started a thread named ... but has
failed to stop it.), not due to completely new or gone warning messages.
"Exception" in output of unit tests
===================================
611 (7.0.57: 603, 7.0.59: 611)
The change in numbers is mostly due to varying number of messages during
tribes tests. In addition, there are three new
"java.net.SocketException: Unexpected end of file from server" starting
in 7.0.59, once for each connector (bio, nio, apr) in
TestAbstractHttp11Processor.testNon2xxResponseWithExpectation().
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
