Am 21.06.2017 um 16:18 schrieb Mark Thomas:
The proposed 9.0.0.M22 release is:
[ ] Broken - do not release
[X] Alpha - go ahead and release as 9.0.0.M22
+1 to release as alpha.
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
- JMX MBean Comparison with 9.0.0.M21 (same as M20):
- Filter MBeans for SetCharacterEncodingFilter are gone
(webapps manager, host-manager and examples)
This is due to r1798121 and r1798125
- New Servlet MBean "responsetrailer" in examples webapp
This is due to r1796186
- Manager MBean attribute sessionAttributeValueClassNameFilter added
for webapp manager and host-manager with value
java\.lang\.(?:Boolean|Integer|Long|Number|String)|org\.apache\.catalina\.filters\.CsrfPreventionFilter\$LruCache(?:\$1)?|java\.util\.(?:Linked)?HashMap
This is due to BZ61150, r1798384
- one more thread is started
- MBean java.util.logging:type=Logging has three items removed
from the LoggerNames array: org.apache.catalina.session,
org.apache.catalina.session.ManagerBase and
org.apache.catalina.session.StandardManager
- Unit tests: No failures, below comparisons are against M20 and M21.
Numbers are given for M20 / M21 / M22.
- Exceptions:
- new java.lang.IllegalStateExceptions:
- M21 (both once):
java.lang.IllegalStateException: Calling [asyncComplete()] is
not valid for a request with Async state [MUST_COMPLETE]
java.lang.IllegalStateException: Unexpected read state [CLOSING]
- M22 (twice):
Exception in thread "testBug54928"
java.lang.IllegalStateException: Calling [asyncComplete()] is not valid
for a request with Async state [MUST_ERROR]
- changed in M22 (was 2 / 1):
org.apache.catalina.core.StandardHostValve.invoke Exception Processing
/simple
instead now once
org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service()
for servlet [simple] in context with path [] threw exception
and the exception is
[junit] java.io.IOException: Stream reset
[junit] at
org.apache.coyote.http2.Stream$StreamInputBuffer.doRead(Stream.java:866)
[junit] at org.apache.coyote.Request.doRead(Request.java:526)
...
- 20 / 26 / 22 java.lang.NullPointerException
- java.io.IOException
- new in M22 (once)
java.security.cert.CertificateException: Could not parse certificate:
java.io.IOException: Incomplete data
Caused by: java.io.IOException: Incomplete data
- 4 / 3 / 3
java.io.IOException: The socket [NUMBER] associated with this connection
has been closed.
- 6 / 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].
- 12 / 12 / 11
java.io.IOException: java.io.IOException: Broken pipe
- 2 / 2 / 3
Caused by: java.io.IOException: Connection reset by peer
- 2 / 1 / 2 java.io.EOFException
- only in M21 (once)
java.util.concurrent.RejectedExecutionException: Executor not running,
can't force a command into the queue
- only in M21 (once)
java.lang.Exception.<init>(Exception.java:LINE)
java.lang.InterruptedException.<init>(InterruptedException.java:LINE)
- only in M21 (once apr) and M22 (once nio)
org.apache.catalina.connector.CoyoteAdapter.asyncDispatch Exception
while processing an asynchronous request
- 2 / 1 / 3
org.apache.catalina.tribes.transport.nio.NioReplicationTask.run
IOException in replication worker, unable to drain channel. Probable
cause: Keep alive socket closed[null].
- 5 / 4 / 5
java.nio.channels.ClosedChannelException
- 7 / 5 / 4
org.apache.catalina.tribes.ChannelException: Sender not connected.; No
faulty members identified.
- 3 / 3 / 2
org.apache.catalina.tribes.ChannelException: Operation has timed
out([NUMBER] ms.).; Faulty members:tcp://{IP}:PORT;
but instead in M22 one new
org.apache.catalina.tribes.ChannelException: Send failed, and sender is
disconnected. Not retrying.; Faulty members:tcp://{IP}:PORT;
- SEVERE messages
- new in M22
org.apache.catalina.valves.SSLValve.invoke The SSL provider specified on
the connector associated with this request of [wontBeFound] is invalid.
The certificate data could not be processed.
together with
java.security.NoSuchProviderException: no such provider: wontBeFound
- 1 / 0 / 1 for apr
org.apache.tomcat.websocket.pojo.PojoEndpointBase.onError No error
handling configured for
[org.apache.tomcat.websocket.TesterEchoServer$Async] and the following
error occurred
- 1 / 0 / 0 for nio
org.apache.tomcat.websocket.pojo.PojoEndpointBase.onError No error
handling configured for
[org.apache.tomcat.websocket.TesterEchoServer$Basic] and the following
error occurred
- 0 / 1(apr) / 1(nio)
org.apache.catalina.connector.CoyoteAdapter.asyncDispatch Exception
while processing an asynchronous request
- 0 / 1 / 1 (jsse-nio)
org.apache.coyote.AbstractProtocol$ConnectionHandler.process Error
reading request, ignored
- 5 / 4 / 4 nio
org.apache.coyote.AbstractProtocol$ConnectionHandler.process Error
reading request, ignored
- 2 / 2 / 4 apr resp. 2 / 2 / 3 nio2
org.apache.coyote.http11.Http11Processor.service Error processing request
- 4 / 3 / 5 apr resp. 8 / 16 / 8 nio resp. 2 / 3 / 3 nio2
org.apache.coyote.http11.Http11Processor.endRequest Error finishing response
- 5 / 4 / 2
org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.memberDisappeared
Unable to start election when member was removed.
- 8 / 7 / 8
org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.messageReceived
Error processing coordination message. Could be fatal.
- WARN messages
- new in M22 (3 times all with values around 700ms)
org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom
Creation of SecureRandom instance for session ID generation using
[SHA1PRNG] took [MMM] milliseconds.
- new in M22
org.apache.catalina.valves.SSLValve.invoke Failed to process certificate
string [-----BEGIN CERTIFICATE-----
followed bysome PEM data and then:
to create a java.security.cert.X509Certificate object
[junit] java.security.cert.CertificateException: Could not parse
certificate: java.io.IOException: Incomplete data
[junit] at
sun.security.provider.X509Factory.engineGenerateCertificate(X509Factory.java:110)
...
[junit] Caused by: java.io.IOException: Incomplete data
[junit] at
sun.security.provider.X509Factory.readOneBlock(X509Factory.java:612)
[junit] at
sun.security.provider.X509Factory.engineGenerateCertificate(X509Factory.java:96)
...
Maybe related to the SEVERE
org.apache.catalina.valves.SSLValve.invoke The SSL provider specified on
the connector associated with this request of [wontBeFound] is invalid.
The certificate data could not be processed.
which follows as the next message.
- only once in M21 for nio2
org.apache.tomcat.util.net.AbstractEndpoint.processSocket Executor
rejected socket
[org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper@HEX:org.apache.tomcat.util.net.Nio2Channel@HEX:sun.nio.ch.UnixAsynchronousSocketChannelImpl[closed]]
for processing
- Only once in M20
[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 [...] milliseconds.
- 3 / 3 / 4
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:
- 7 / 7 / 8
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads
The web application [ROOT] appears to have started a thread named
[Thread-...] but has failed to stop it. This is very likely to create a
memory leak. Stack trace of thread
- 15 / 10 / 11
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads
The web application [ROOT] appears to have started a thread named
[pool-P-thread-...] but has failed to stop it. This is very likely to
create a memory leak. Stack trace of thread
- 1 / 2 / 1
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads
The web application [ROOT] appears to have started a thread named
[http-...-127.0.0.1-auto-...-exec-...] but has failed to stop it. This
is very likely to create a memory leak. Stack trace of thread
(M20: 1xnio, M21: 1xapr, 1xnio2, M22: 1xnio)
- 2 / 3 / 3
org.apache.catalina.tribes.transport.nio.ParallelNioSender.doLoop Member
send is failing for:[tcp://{IP}:PORT] ; Setting to suspect and retrying.
- 1 / 0 / 1
org.apache.catalina.tribes.transport.nio.ParallelNioSender.doLoop Not
retrying send for:[tcp://{IP}:PORT]; Sender is disconnected.
M20: Tribes-Task-Receiver-..., M22: Membership-MemberDisappeared
- 2 / 1 / 3
org.apache.catalina.tribes.transport.nio.NioReplicationTask.run
IOException in replication worker, unable to drain channel. Probable
cause: Keep alive socket closed[null].
- 8 / 5 / 5
org.apache.catalina.tribes.transport.nio.ParallelNioSender.doLoop Member
send is failing for:[tcp://{IP}:PORT] ; Setting to suspect and retrying.
- 44 / 33 / 27
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={...}, ]]
- 6 / 5 / 4
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={...}, ]]
- 1 / 0 / 0
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={...}, ]]
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.6.2 (!) and OpenSSL 1.0.2l 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
