On 13.02.2013 00:22, Mark Thomas wrote:
> The proposed Apache Tomcat 7.0.37 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.37/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-227/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_37/
>
> The proposed 7.0.37 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.37 Stable
+1 to release.
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
- warning in
test/org/apache/catalina/core/TestStandardContextResources.java:
uses unchecked or unsafe operations
Same as for 7.0.35, where it was new.
- build result looks consistent with binaries
- no checkstyle complaints
- some Javadoc warnings (only in jdbc-pool, not a regression)
- Unit tests
- no error or failures
- some warnings (see below), one new warning type
concerning NPE in CoyoteAdapter when calling access log
- JMX MBean-Comparison OK
- OpenFileDescriptorCount up from 57 to 61 (same as before 7.0.35)
- fewer Loggers (37 instead of 44), removed Loggers are:
- websocket, websocket.snake, websocket.snake.SnakeWebSocketServlet
- async, async.Async0, async.Async1, async.Async2
Build and tests were done using Java 1.6.0_39. OS was Solaris 10 Sparc,
tcnative was 1.1.27 based on APR 1.4.6 and OpenSSL 1.0.1e (plus a few
patches).
Unit test warnings (very similar to 7.0.35 and before):
- Fixed now (problem in 7.0.35): Exception while attempting to add
an entry to the access log
in org.apache.catalina.connector.CoyoteAdapter log
while running org.apache.el.TestELInJsp and
org.apache.jasper.compiler.TestParser.
- org.apache.catalina.deploy.TestWebXmlOrdering
- BIO, NIO and APR: [main]
org.apache.catalina.deploy.WebXml.orderWebFragments Used a wrong
fragment name z at web.xml absolute-ordering tag!
- org.apache.tomcat.util.net.TestCustomSsl
- BIO twice "Exception getting SSL attributes"
in org.apache.coyote.http11.Http11Processor actionInternal
exception is:
javax.net.ssl.SSLProtocolException: handshake alert: no_certificate
- NIO twice "WARNING: Exception re-negotiating SSL connection"
in org.apache.coyote.http11.Http11NioProcessor actionInternal
- tribes: several warnings, roughly same number as before,
some changed their text
Unit test SEVERE messages: 228 total (+3), still 35 unique messages
Most of those are of type "Servlet.service() for servlet ... threw
exception" (137 times).
The SEVERE message "Error processing request" with an NPE new in 7.0.35
is gone now.
"Exception" in output of unit tests: 218 times (-2), of these 75 times
"javax.servlet.ServletException: Opps."
I'm not claiming that any of the SEVERE or Exception messages are
important. Total numbers of warnings, SEVERE and exceptions are
about the same than for previous releases.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
