Am 21.06.2017 um 23:37 schrieb Mark Thomas:
The proposed 8.5.16 release is: [ ] Broken - do not release [X]
Stable - go ahead and release as 8.5.16
+1 to release.
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
- warning about unchecked calls or conversions in:
- org/apache/catalina/tribes/tipis/AbstractReplicatedMap.java
- org/apache/tomcat/jdbc/pool/PoolProperties.java
Not a regression
- build result looks consistent with binaries
- no checkstyle complaints
- no Javadoc warnings
- JMX MBean Comparison with 8.5.15 (same as 8.5.14):
- 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, r1798385
- 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
- ThreadPool MBean new attributes acceptCount, connectionLinger
and connectionTimeout
- ProtocolHandler MBean new attributes acceptCount and
connectionLinger
- Unit tests: No failures, below comparisons are against 8.5.14 and 8.5.15
Numbers are given for 14 / 15 / 16.
- Exceptions:
- new java.lang.IllegalStateExceptions:
- 15 (once):
java.lang.IllegalStateException: Calling [asyncComplete()] is not valid
for a request with Async state [MUST_COMPLETE]
- 15 (once)
java.lang.IllegalStateException: Cannot call sendError() after the
response has been committed
- 16 (once):
Exception in thread "testBug54928" java.lang.IllegalStateException:
Calling [asyncComplete()] is not valid for a request with Async state
[DISPATCHED]
- 16 (once)
java.lang.IllegalStateException: Unexpected read state [CLOSING]
- 1 / 0 / 1
org.apache.catalina.core.StandardHostValve.invoke Exception Processing
/simple
- new in 16
Exception in thread "http-apr-127.0.0.1-auto-I-exec-PPPPP"
java.lang.NullPointerException
- 9 / 7 / 10
java.lang.NullPointerException
- java.io.IOException
- new in M22 (3 times)
java.security.cert.CertificateException: Unable to initialize,
java.io.IOException: extra data given to DerValue constructor
java.io.IOException: extra data given to DerValue constructor
maybe related to the error following next:
java.security.NoSuchProviderException: no such provider: wontBeFound
- 5 / 5 / 6
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].
- 11 / 11 / 12
java.io.IOException: java.io.IOException: Broken pipe
- 1 / 2 / 2
java.io.EOFException
- only in 8.5.15 (once)
java.util.concurrent.RejectedExecutionException: Executor not running,
can't force a command into the queue
- in 8.5.14 (once apr) 8.5.15 (once apr and nio each)
and 8.5.16 (once nio)
org.apache.catalina.connector.CoyoteAdapter.asyncDispatch Exception
while processing an asynchronous request
- 6 / 3 / 0
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
- 9 / 7 / 6
org.apache.catalina.tribes.ChannelException: Sender not connected.; No
faulty members identified.
- 2 / 4 / 2
org.apache.catalina.tribes.ChannelException: Operation has timed
out([NUMBER] ms.).; Faulty members:tcp://{IP}:PORT;
- 5 / 1 / 0
org.apache.catalina.tribes.ChannelException: java.net.ConnectException:
Connection refused; Faulty members:tcp://{IP}:PORT;
Caused by: java.net.ConnectException: Connection refused
- SEVERE messages
- new in 16 (3 times)
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.
- 1 / 0 / 1 (nio)
org.apache.catalina.core.StandardHostValve.invoke Exception Processing
/simple
- 1 / 0 / 1 (nio2 / nio)
org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service()
for servlet [simple] in context with path [] threw exception
- 1(apr) / 1xapr+2xnio / 1(nio)
org.apache.catalina.connector.CoyoteAdapter.asyncDispatch Exception
while processing an asynchronous request
- 4(apr) / 4(apr) / 5(apr)+1(jsse-nio)
org.apache.coyote.AbstractProtocol$ConnectionHandler.process Error
reading request, ignored
- 2xapr+2xnio / 1xnio+2xnio2 / 2xapr+2xnio2
org.apache.coyote.http11.Http11Processor.endRequest Error finishing response
- 5 / 5 / 2
org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.memberDisappeared
Unable to start election when member was removed.
- 11 / 7 / 6
org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.messageReceived
Error processing coordination message. Could be fatal.
- WARN messages
- new in 16
org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom
Creation of SecureRandom instance for session ID generation using
[...] took [...] milliseconds.
for [SHA1PRNG] 3 times on main thread taking about 550 ms, 5
times on localhost-startStop-1 thread taking about 100-150ms.
For [INSECURE] two times on localhost-startStop-1 thread taking
about 100-150ms.
- new in 16
org.apache.catalina.valves.SSLValve.invoke Failed to process certificate
string [-----BEGIN CERTIFICATE-----
followed by some PEM data and then:
[junit] ] to create a java.security.cert.X509Certificate object
[junit] java.security.cert.CertificateException: Unable to
initialize, java.io.IOException: extra data given to DerValue constructor
[junit] at
sun.security.x509.X509CertImpl.<init>(X509CertImpl.java:199)
...
[junit] Caused by: java.io.IOException: extra data given to
DerValue constructor
[junit] at sun.security.util.DerValue.init(DerValue.java:384)
[junit] at sun.security.util.DerValue.<init>(DerValue.java:294)
[junit] at
sun.security.x509.X509CertImpl.<init>(X509CertImpl.java:196)
...
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 15 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 16, note appliacation name "test"
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads
The web application [test] 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:
- 3 / 2 / 3
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 / 6 / 7
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:
- 8 / 9 / 8
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:
- 2 / 4 / 2
org.apache.catalina.tribes.transport.nio.ParallelNioSender.doLoop Member
send is failing for:tcp://{IP}:PORT ; Setting to suspect and retrying.
- 6 / 3 / 0
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.
- 48 / 42 / 39
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={...}, ]
- 9 / 7 / 6
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={...}, ]
- 9 / 8 / 6
org.apache.catalina.tribes.transport.nio.ParallelNioSender.doLoop Member
send is failing for:tcp://{IP}:PORT ; Setting to suspect and retrying.
Build and tests were done using Java 1.7.0_80. 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
