tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <>
Subject Re: [VOTE] Release Apache Tomcat 7.0.40
Date Mon, 06 May 2013 08:28:11 GMT
On 05.05.2013 12:44, Mark Thomas wrote:
> The proposed Apache Tomcat 7.0.40 release is now available for voting.
> It can be obtained from:
> The Maven staging repo is:
> The svn tag is:
> The proposed 7.0.40 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.40 Stable

+1 to release.


- MD5 OK
- signatures OK
- key in KEYS file
- gz and zip for src and bin consistent
- src completely consistent with svn tag
  - except line ends in 4 jspx files (missing eol-style)
    fixed now in r1479483.
- builds fine
  - warning about unsafe or unchecked operations in:
    - javax/el/
    - org/apache/catalina/core/
    - org/apache/catalina/tribes/tipis/
      (14 times)
    - org/apache/catalina/ha/context/
    - org/apache/catalina/ha/session/
    - org/apache/coyote/http11/
  Same as for 7.0.39 plus http11.AbstractHttp11Processor.
- build result looks consistent with binaries
- no checkstyle complaints
- some Javadoc warnings
  - only one remaining in jdbc-pool, better than before
- Unit tests no errors or failures
  - the previous SEVERE message (144 times) with exception stack in
    Echo servlet when running TestInputBuffer is now fixed.
- JMX MBean-Comparison OK
  - unchanged except new tools.jar in jarsToSkip

Build and tests were done using Java 1.6.0_45. OS was Solaris 10 Sparc,
tcnative was 1.1.27 based on APR 1.4.6 and OpenSSL 1.0.1e (plus a few

Unit test warnings (very similar to 7.0.35 and before):

- 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!

  - BIO twice "Exception getting SSL attributes"
    in org.apache.coyote.http11.Http11Processor actionInternal
    exception is: handshake alert: no_certificate
  - NIO twice "WARNING: Exception re-negotiating SSL connection"
    in org.apache.coyote.http11.Http11NioProcessor actionInternal

- tribes: several warnings (18), numbers down to the level of 7.0.38
  after the temporary rise in 7.0.39

Unit test SEVERE messages: 225 total (-141). The drop is due to
silencing the Echo servlet. We are now back to 7.0.37 numbers.

About 20 unique messages.

Most of those are of type "Servlet.service() for servlet ... threw
exception" (137 times, unchanged).

Second biggest block:

Count    message
  27     [junit] TIMESTAMP SEVERE [main]
org.apache.tomcat.util.digester.Digester.startElement Begin event threw
   3     [junit] TIMESTAMP SEVERE [main]
org.apache.tomcat.util.digester.Digester.endElement End event threw

Third biggest block is 24 messages from the mem leak detection during
context unload.

"Exception" in output of unit tests: 217 times (-286, most due to fixed
Echo servlet). Numbers are now back to the lower 7.0.37 range.

Top exception counts:

  75     [junit] javax.servlet.ServletException: Opps.
   9     [junit] Invalid CRLF, no CR character
   9     [junit]  java.lang.IllegalArgumentException: <ordering> element
is limited to 1 occurrence
   9     [junit]  java.lang.IllegalArgumentException: <name> element is
limited to 1 occurrence
   9     [junit]  java.lang.IllegalArgumentException:
<absolute-ordering> element is limited to 1 occurrence
   6     [junit] org.apache.jasper.JasperException:
/bug49nnn/bug49297DuplicateAttr.jsp (line: 21, column: 46) Attribute
qualified names must be unique within an element

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.



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message