Am 12.04.2017 um 22:11 schrieb Mark Thomas:
The proposed Apache Tomcat 9.0.0.M20 release is now available for voting.

This is a milestone release for the 9.0.x branch. It should be
noted that, as a milestone release:
- Servlet 4.0 is not finalised
- The EGs have not started work on JSP 2.4, EL 3.1 or WebSocket 1.2/2.0

The major changes compared to the 9.0.0.M19 release are:

- Correct a regression that broke JMX operations (including the Manager
  web application) if the operation took parameters

- Add JMX support for Tribes components

- Calls to isReady() no longer throw exceptions after timeouts for async
  servlets


Along with lots of other bug fixes and improvements

For full details, see the changelog:
http://svn.apache.org/repos/asf/tomcat/trunk/webapps/docs/changelog.xml

It can be obtained from:
https://dist.apache.org/repos/dist/dev/tomcat/tomcat-9/v9.0.0.M20/
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-1131/
The svn tag is:
http://svn.apache.org/repos/asf/tomcat/tags/TOMCAT_9_0_0_M20/

The proposed 9.0.0.M20 release is:
[ ] Broken - do not release
[X] Alpha - go ahead and release as 9.0.0.M20

+1 to release as alpha.

The new NPE observed in M19 are now back to a normal level (count 38 down to 20).

Details
=======

- SHA1 and MD5 OK
- signatures OK
- key in KEYS file
- gz and zip for src and bin consistent
- src consistent with svn tag
  - except bin shell scripts are not executable in src tarball
    (not critical)
- builds fine
- build result looks consistent with binaries
- no checkstyle complaints
- no Javadoc warnings
- Unit tests: No failures, below comparisons are against M19.

  - variable data in messages now often contained in "[]" (expected)

  - Exception:
    - no longer happens for NIO (occurred once for NIO in M19):

org.apache.catalina.connector.CoyoteAdapter.asyncDispatch Exception while processing an asynchronous request java.lang.IllegalStateException: The request associated with the AsyncContext has already completed processing.

    - 18 less (38->20) java.lang.NullPointerException

    - one more (11->12) java.io.IOException: Broken pipe

- one more (5->6) java.io.IOException: java.io.IOException: Unexpected error [NUMBER] writing data to the APR/native socket [NUMBER] with wrapper [org.apache.tomcat.util.net.AprEndpoint$AprSocketWrapper@HEX:NUM].

    - one more (4->5) java.nio.channels.ClosedChannelException

- one more (3->4) java.io.IOException: The socket [NUMBER] associated with this connection has been closed.

- one more (2->3) org.apache.catalina.tribes.ChannelException: java.net.ConnectException: Connection refused; Faulty members:tcp://{IP}:PORT;

- one more (1->2) for NIO: org.apache.catalina.core.StandardHostValve.invoke Exception Processing /simple

- two less (4->2) org.apache.catalina.tribes.transport.nio.NioReplicationTask.run IOException in replication worker, unable to drain channel. Probable cause: Keep alive socket closed[null].

  - SEVERE messages

- new (once for APR and NIO) org.apache.tomcat.websocket.pojo.PojoEndpointBase.onError No error handling configured for [org.apache.tomcat.websocket.TesterEchoServer$Async] and the following error occurred

- one more for NIO (1->2) org.apache.catalina.core.StandardHostValve.invoke Exception Processing /simple

- 4 more (1->5) org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.memberDisappeared Unable to start election when member was removed.

- 3 less (11->8) org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.messageReceived Error processing coordination message. Could be fatal.

- 2 less for APR (5->4), one more for NIO (4->5) org.apache.coyote.AbstractProtocol$ConnectionHandler.process Error reading request, ignored

- 4 less for APR (6->2), 8 less for NIO (10->2) org.apache.coyote.http11.Http11Processor.service Error processing request

- 3 less for APR (7->4), 5 less for NIO (13->8), 2 more for NIO2 (0->2) org.apache.coyote.http11.Http11Processor.endRequest Error finishing response

  - WARN messages

- one new [ContainerBackgroundProcessor[StandardEngine[Tomcat].StandardHost[localhost].StandardContext[]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread [http-apr-127.0.0.1-auto-I-exec-PPPPP] (id=[NUMBER]) was previously reported to be stuck but has completed. It was active for approximately [MMM] milliseconds.

- one new org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] 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. Stack trace of thread:

- one more (3->4) [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation. Stack trace of request processing thread:

- one more (6->7) [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [Thread-T] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:

- one more (14->15) [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [pool-P-thread-T] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:

- two more (1->3) [Membership-MemberDisappeared.] org.apache.catalina.tribes.transport.nio.ParallelNioSender.doLoop Member send is failing for:tcp://{IP}:PORT ; Setting to suspect and retrying.

- no more (was once) [Tribes-Task-Receiver-T] org.apache.catalina.tribes.transport.nio.NioReplicationTask.sendAck Unable to send ACK back through channel, channel disconnected?: null

- two less (4-<2) [Tribes-Task-Receiver-T] org.apache.catalina.tribes.transport.nio.NioReplicationTask.run IOException in replication worker, unable to drain channel. Probable cause: Keep alive socket closed[null].

- two less (10->8) [Tribes-Task-Receiver-T] org.apache.catalina.tribes.transport.nio.ParallelNioSender.doLoop Member send is failing for:tcp://{IP}:PORT ; Setting to suspect and retrying.

- 4 less (48->44) [Tribes-Task-Receiver-T] org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.sendElectionMsgToNextInline Unable to send election message to:[org.apache.catalina.tribes.membership.MemberImpl[tcp://{IP}:PORT,{IP},PORT, alive=AAA, securePort=-1, UDP Port=-1, id={...}, payload={}, command={}, domain={...}, ]]


- JMX MBean Comparison with 9.0.0.M19: no changes

Build and tests were done using Java 1.8.0_121. OS was Solaris 10 Sparc, tcnative was 1.2.12 based on APR 1.5.2 and OpenSSL 1.0.2k plus patches.

Thanks for RM and 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