On 19.11.2012 00:34, Mark Thomas wrote:
> The proposed Apache Tomcat 7.0.33 release is now available for voting.
> 
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.33/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-043/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_33/
> 
> The proposed 7.0.33 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.33 Stable

+1 to release

Most notable observation:

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
- build result looks consistent with binaries
- no checkstyle complaints
- some Javadoc warnings (only in jdbc-pool, see below)
- Unit tests
  - broken test TestAccessLogValve fixed in head, only a test problem
  - one APR test failure TestWebdavServlet started to loop.
    Messages see below. Hopefully fixed in future version by Mladens
    recent tcnative fixes.
  - some warnings (see below)
- JMX MBean-Comparison OK

Build and tests were done using Java 1.6.0_37. OS was Solaris 10 Sparc,
tcnative was 1.1.24 based on APR 1.4.6 and OpenSSL 1.0.1c (plus two
patches).

- Some Javadoc Warnings in jdbc-pool (not a regression)

Unit test warnings (except for tribes all of those look like 7.0.32 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!

- 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

Unit test SEVERE messages: 229 total, about 40 unique messages
Most of those are of type "Servlet.service() for servlet ... threw
exception".


"Exception" in output of unit tests: 216 times, of these 75 times
"javax.servlet.ServletException: Opps."

I'm not claiming that any of the SEVERE or Exception messages are new
ones or important.

Regards,

Rainer

Log output of Unit test failure (loop in TestWebdavServlet):

    [junit] INFO: Pausing ProtocolHandler
["http-apr-127.0.0.1-auto-2-56276"]
    [junit] Nov 19, 2012 6:53:35 PM
org.apache.catalina.core.StandardService stopInternal
    [junit] INFO: Stopping service Tomcat
    [junit] Nov 19, 2012 6:53:35 PM
org.apache.catalina.core.ApplicationContext log
    [junit] INFO: SessionListener: contextDestroyed()
    [junit] Nov 19, 2012 6:53:35 PM
org.apache.catalina.core.ApplicationContext log
    [junit] INFO: ContextListener: contextDestroyed()
    [junit] Nov 19, 2012 6:53:35 PM org.apache.coyote.AbstractProtocol stop
    [junit] INFO: Stopping ProtocolHandler
["http-apr-127.0.0.1-auto-2-56276"]
    [junit] Nov 19, 2012 6:53:35 PM
org.apache.tomcat.util.net.AprEndpoint$Poller doPoll
    [junit] SEVERE: Critical poller failure (restarting poller): [9] Bad
file number


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to