On 22.03.2013 17:48, Mark Thomas wrote:
> The proposed Apache Tomcat 7.0.39 release is now available for voting.
>
> It can be obtained from:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.39/
> The Maven staging repo is:
> https://repository.apache.org/content/repositories/orgapachetomcat-015/
> The svn tag is:
> http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_39/
>
> The proposed 7.0.39 release is:
> [ ] Broken - do not release
> [ ] Stable - go ahead and release as 7.0.39 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
Same as for 7.0.38 minus fileupload.FileCleaningTracker
- build result looks consistent with binaries
- no checkstyle complaints
- some Javadoc warnings
- some in jdbc-pool, not a regression
- new ones:
- 9 in package java/org/apache/tomcat/util/http/fileupload/,
one due to a missing delete(File) method in FileDeleteStrategy,
all others due to links containing the original fileupload
commons package name no longer valid.
- Unit tests no errors or failures
- one 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. It first showed up
in 7.0.38.
- JMX MBean-Comparison OK (unchanged)
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, a slightly higher number as before,
types of warnings did exist in 7.0.38, one of the old
didn't show up
Unit test SEVERE messages: 366 total (+3). The new ones are some
slighty more frequent messages in tribes. The very frequent one
that was new in 7.0.38 (135 times) is still there:
"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 20 unique messages.
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: 503 times (+3).
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
