On 06.06.2013 14:06, Mark Thomas wrote:
> The proposed Apache Tomcat 7.0.41 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.41/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-073/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_41/
>
> The proposed 7.0.41 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.41 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 about unsafe or unchecked operations in:
- javax/el/ResourceBundleELResolver.java:108
- org/apache/catalina/core/AsyncContextImpl.java:274
- org/apache/catalina/tribes/tipis/AbstractReplicatedMap.java
(14 times)
- org/apache/catalina/ha/context/ReplicatedContext.java:66
- org/apache/catalina/ha/session/BackupManager.java:169
- org/apache/catalina/filters/CsrfPreventionFilter.java:180
-
org/apache/catalina/tribes/group/interceptors/TwoPhaseCommitInterceptor.java:119
- org/apache/coyote/http11/AbstractHttp11Processor.java:823
Same as for 7.0.40 plus CsrfPreventionFilter.
- build result looks consistent with binaries
- no checkstyle complaints
- only one Javadoc warning
- in jdbc-pool: DataSourceProxy.java:544: 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.6 and OpenSSL 1.0.1e (plus a few
patches).
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!
- 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 (26), numbers slightly up (+8) relative to
7.0.40, but same types of messages.
Unit test SEVERE messages: 225 total (unchanged).
About 17 unique messages (-3).
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
exception
3 [junit] TIMESTAMP SEVERE [main]
org.apache.tomcat.util.digester.Digester.endElement End event threw
exception
Third biggest block is 27 messages from the mem leak detection during
context unload.
"Exception" in output of unit tests: 214 times (-3).
Top exception counts:
75 [junit] javax.servlet.ServletException: Opps.
9 [junit] java.io.IOException: Invalid CRLF, no CR character
encountered.
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.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
