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.42
Date Tue, 02 Jul 2013 20:01:31 GMT
On 02.07.2013 11:18, Mark Thomas wrote:
> The proposed Apache Tomcat 7.0.42 release is now available for voting.
> It can be obtained from:
> The Maven staging repo is:
> The svn tag is:
> The proposed 7.0.42 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.42 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
- 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/catalina/filters/
    - org/apache/coyote/http11/
    - org/apache/catalina/core/
    - org/apache/catalina/realm/
  Same as for 7.0.41 plus ApplicationContext plus JAASRealm.
- build result looks consistent with binaries
- no checkstyle complaints
- only one Javadoc warning
  - in jdbc-pool: warning - Tag @link: can't
find getParentLogger in javax.sql.DataSource
- Unit tests no errors or failures
- JMX MBean-Comparison OK (unchanged)

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.8 and OpenSSL 1.0.1e (plus a few

Unit test warnings (very similar to 7.0.35 and before, but two new ones,
one NPE in access log, one testResources warning):

- 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

- org.apache.catalina.core.TestStandardContextResources testResources
  - BIO, NIO and APR: testResources(): orderedLibs:
[hamcrest-core-1.3.jar, resources.jar, resources2.jar]

- org.apache.catalina.connector.CoyoteAdapter log
  Exception while attempting to add an entry to the access log
    [junit] java.lang.NullPointerException
    [junit]     at
    [junit]     at
    [junit]     at ...

- tribes: several warnings (19), numbers slightly down (-7) from 7.0.41
but the same (+1) as 7.0.40. Same types of messages.

Unit test SEVERE messages: 221 total (-4).

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 19 (-8) messages from the mem leak detection
during context unload.

"Exception" in output of unit tests: 219 times (+5).

Top exception counts (unchanged):

  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