Mark, On 10/3/12 5:24 AM, Mark Thomas wrote: > The proposed Apache Tomcat 7.0.32 release is now available for voting. > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.32/ > The Maven staging repo is: > https://repository.apache.org/content/repositories/orgapachetomcat-087/ > The svn tag is: > http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_32/ > > The proposed 7.0.32 release is:
[X] Stable - go ahead and release 7.0.32 as Stable
- [Ubuntu Linux 2.6.32, Oracle Java 1.6.0_26 64-bit, gcc 4.4.5, APR
1.4.2, OpenSSL 0.9.8o]
- MD5 sums match
- GPG signatures match
- Source ZIP and tarball are the same
- Source compiles cleanly
- Bundled tcnative compiles cleanly
- Checkstyle passes
I did however get a unit test failure: details below. I'll check to see
if it is repeatable.
Thanks,
-chris
Testsuite:
org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak
Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 2.047 sec
------------- Standard Output ---------------
class java.lang.Thread [pool-1-thread-4] EXITING
class java.lang.Thread [pool-1-thread-1] EXITING
class java.lang.Thread [pool-1-thread-3] EXITING
class java.lang.Thread [pool-1-thread-2] EXITING
class java.lang.Thread [pool-1-thread-5] EXITING
------------- ---------------- ---------------
------------- Standard Error -----------------
Oct 3, 2012 12:17:12 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-127.0.0.1-auto-1"]
Oct 3, 2012 12:17:12 PM org.apache.catalina.core.StandardService
startInternal
INFO: Starting service Tomcat
Oct 3, 2012 12:17:12 PM org.apache.catalina.core.StandardEngine
startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.32
Oct 3, 2012 12:17:12 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-127.0.0.1-auto-1-44459"]
Oct 3, 2012 12:17:12 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named
[pool-1-thread-1] but has failed to stop it. This is very likely to
create a memory leak.
Oct 3, 2012 12:17:12 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named
[pool-1-thread-3] but has failed to stop it. This is very likely to
create a memory leak.
Oct 3, 2012 12:17:13 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-127.0.0.1-auto-1-44459"]
Oct 3, 2012 12:17:13 PM org.apache.catalina.core.StandardService
stopInternal
INFO: Stopping service Tomcat
Oct 3, 2012 12:17:13 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-bio-127.0.0.1-auto-1-44459"]
Oct 3, 2012 12:17:13 PM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-bio-127.0.0.1-auto-1-44459"]
------------- ---------------- ---------------
Testcase: testTimerThreadLeak took 2.024 sec
FAILED
null
junit.framework.AssertionFailedError: null
at
org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak.testTimerThreadLeak(TestWebappClassLoaderExecutorMemoryLeak.java:72)
signature.asc
Description: OpenPGP digital signature
