On 07.03.2013 23:47, Mark Thomas wrote:
> The proposed Apache Tomcat 7.0.38 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.38/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-002/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_38/
>
> The proposed 7.0.38 release is:
> [ ] Broken - do not release
> [X] Stable - go ahead and release as 7.0.38 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:268
- 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/tribes/group/interceptors/TwoPhaseCommitInterceptor.java:119
- org/apache/tomcat/util/http/fileupload/FileCleaningTracker.java:243
Didn't check whether they are new (I expect not)
- build result looks consistent with binaries
- no checkstyle complaints
- some Javadoc warnings
- some in jdbc-pool, not a regression
- new ones:
- java/org/apache/tomcat/util/buf/UEncoder.java:67: warning -
@param argument "buf" is not a parameter name.
- two in package java/org/apache/tomcat/util/http/fileupload/disk/,
which are probably due to "javadoc: warning - Error fetching URL:
http://commons.apache.org/io/api-release/package-list";. Indeed
that URL responds with a redirect and then a "Not Found".
- Unit tests
- one error in TestB2CConverter due to an unexpected internal
charset "COMPOUND_TEXT" which we should exclude from the test.
All other charsets pass the test.
- one new SEVERE message 144 times with exception stack in Echo
servlet when running TestInputBuffer, details below.
It would be nice to get rid of that one.
- JMX MBean-Comparison OK
- again fewer Loggers (35 instead of 37), removed Loggers are:
- C2BConverter and for its package org.apache.tomcat.util.buf
- expected new attributes requestCount, errorCount, minTime and
maxTime on the per-Webapp MBean
- jarsToSkip: removed entries due to r1448831 (no longer scan
bootstrap class path by default) are:
access-bridge.jar,access-bridge-64.jar,dnsns.jar,jaccess.jar,
ldapsec.jar,localedata.jar,sunjce_provider.jar,
sunmscapi.jar,sunpkcs11.jar,jhall.jar,tools.jar,
sunec.jar,zipfs.jar,gnome-java-bridge.jar,
pulse-java.jar,apple_provider.jar,AppleScriptEngine.jar,
CoreAudio.jar,dns_sd.jar,j3daudio.jar,j3dcore.jar,
j3dutils.jar,jai_core.jar,jai_codec.jar,
mlibwrapper_jai.jar,MRJToolkit.jar,vecmath.jar
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):
- 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, about the same number as before,
some changed their text
Unit test SEVERE messages: 363 total (+135). The new ones are probably
all due to 144 times
"SEVERE: Servlet.service() for servlet [Echo] in context with path []
threw exception"
It happens in org.apache.catalina.connector.TestInputBuffer for all
connectors and the exception is
[junit] java.nio.charset.MalformedInputException: Input length = 1
[junit] at
java.nio.charset.CoderResult.throwException(CoderResult.java:260)
...
which wasn't there in the previous release.
About 30 unique messages (down by about 5, mostly tribes).
Most of those are of type "Servlet.service() for servlet ... threw
exception" (137 times + the 144 new Echo servlet ones).
"Exception" in output of unit tests: 500 times (+282), all of these
additional ones due to the Echo servlet exception described above.
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
