Am 28.03.2017 um 18:45 schrieb Violeta Georgieva:
The proposed Apache Tomcat 7.0.77 release is now available for voting.

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-7/v7.0.77/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1128/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_77/

The proposed 7.0.77 release is:
[ ] Broken - do not release
[X] Stable - go ahead and release as 7.0.77 Stable

+1 to release, thanks for RM.

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
   - warnings about unchecked calls or conversions in:
     - o.a.t.dbcp
     - javax/el/ResourceBundleELResolver.java
   Both not a regression
- build result looks consistent with binaries
- no checkstyle complaints
- no Javadoc warnings
- Unit tests: no errors or failures

  - ERROR message:
    - fewer "ERROR:null" (4 versus 2)
- new "org.apache.catalina.core.AprLifecycleListener.initializeSSLnull" (once)
    - new "org.apache.catalina.core.StandardWrapperValve.eventnull" (once)

  - WARN messages
    - more tribes (50 versus 60)
  - SEVERE messages
- new "SEVERE: Servlet.service() for servlet [comet] in context with path [] threw exception" (once) - no more "org.apache.catalina.connector.CoyoteAdapter.asyncDispatch An exception or error occurred in the container during the request processing" - new "org.apache.tomcat.websocket.pojo.PojoEndpointBase.onError No error handling configured for [org.apache.tomcat.websocket.TesterEchoServer$Basic] and the following error occurred" (once) - fewer "org.apache.catalina.core.StandardWrapperValve.event Servlet.service() for servlet [comet] in context with path [] threw exception" (6 versus 4) fewer "org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.memberDisappeared Unable to start election when member was removed." (6 versus 5) - fewer "org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [] appears to have started a thread named [http-nio-127.0.0.1-auto-I-exec-PPPPP] but has failed to stop it. This is very likely to create a memory leak." (12 versus 3) - new "org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [] appears to have started a thread named [WebSocketServer-ROOT-2] but has failed to stop it. This is very likely to create a memory leak." (once)

- JMX MBean Comparison with 7.0.75:
  - ThreadPool MBean attribute currentThreadCount changed
    from 0 to 10 (ajp) resp. 1 to 10 (http)
  - Threading MBean analogously shows 19 more daemon threads
  - ProtocolHandler MBean for http new attribute
"compressibleMimeType: text/html,text/xml,text/plain,text/css,text/javascript,application/javascript"


Build and tests were done using Java 1.6.0_45, java.7.home was pointing
to 1.7.0_80. OS was Solaris 10 Sparc, tcnative was 1.2.12 based on APR 1.5.2 and OpenSSL 1.0.2k.


Regards,

Rainer

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

Reply via email to