2015-10-19 14:16 GMT+03:00 Mark Thomas <ma...@apache.org>: > On 17/10/2015 15:54, Konstantin Kolinko wrote: >> 2015-10-17 10:48 GMT+03:00 Bill Barker <billbar...@apache.org>: >>> To whom it may engage... >>> >>> This is an automated request, but not an unsolicited one. For >>> more information please visit http://gump.apache.org/nagged.html, >>> and/or contact the folk at gene...@gump.apache.org. >>> >>> Project tomcat-trunk-test-apr has an issue affecting its community >>> integration. >>> This issue affects 1 projects, >>> and has been outstanding for 23 runs. >>> The current state of this project is 'Failed', with reason 'Build Timed >>> Out'. >>> For reference only, the following projects are affected by this: >>> - tomcat-trunk-test-apr : Tomcat 9.x, a web server implementing the >>> Java Servlet 4.0, >>> ... >>> >>> >>> Full details are available at: >>> >>> http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test-apr/index.html >>> >>> That said, some information snippets are provided here. >>> >>> The following annotations (debug/informational/warning/error messages) were >>> provided: >>> -DEBUG- Dependency on commons-daemon exists, no need to add for property >>> commons-daemon.native.src.tgz. >>> -DEBUG- Dependency on commons-daemon exists, no need to add for property >>> tomcat-native.tar.gz. >>> -INFO- Failed with reason build timed out >>> -INFO- Project Reports in: >>> /srv/gump/public/workspace/tomcat-trunk/output/logs-APR >>> -INFO- Project Reports in: >>> /srv/gump/public/workspace/tomcat-trunk/output/test-tmp-APR/logs >>> -WARNING- No directory >>> [/srv/gump/public/workspace/tomcat-trunk/output/test-tmp-APR/logs] >>> >>> >>> >>> The following work was performed: >>> http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test-apr/gump_work/build_tomcat-trunk_tomcat-trunk-test-apr.html >>> Work Name: build_tomcat-trunk_tomcat-trunk-test-apr (Type: Build) >>> Work ended in a state of : Failed >>> Elapsed: 1 hour 1 sec >> >> From stdout output, testing started at 06:49 >> The tail of stdout is cited below. The times are around 07:11. The >> last test name mentioned is >> >> Running org.apache.coyote.http11.filters.TestChunkedInputFilter >> ... >> org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case >> [testChunkSizeLong] >> >> Apparently it hung after that and was killed 35 minutes later. > > The last few runs have consistently failed at the same place. > > Can anyone reproduce this locally? (I haven't tried yet.)
An idea: maybe add a StuckThreadDetectionValve into configuration of that test? My expectation is that it will print a stacktrace of the hanging thread so that we have a clue where the hang is. Trunk/Nio2 today failed at [concat] Testsuites with failed tests: [concat] TEST-org.apache.coyote.http2.TestHttp2Section_5_3.NIO2.txt [concat] TEST-org.apache.tomcat.websocket.TestWebSocketFrameClientSSL.NIO2.txt In TEST-org.apache.coyote.http2.TestHttp2Section_5_3.NIO2: Testcase: testWeighting took 10.618 sec FAILED Larger than expected body: [21-Body-5 ] junit.framework.AssertionFailedError: Larger than expected body: [21-Body-5 ] at org.apache.coyote.http2.TestHttp2Section_5_3.testWeighting(TestHttp2Section_5_3.java:168) In TEST-org.apache.tomcat.websocket.TestWebSocketFrameClientSSL.NIO2: Testcase: testBug56032 took 22.502 sec FAILED There are [1] connections still open junit.framework.AssertionFailedError: There are [1] connections still open at org.apache.tomcat.websocket.TestWebSocketFrameClientSSL.testBug56032(TestWebSocketFrameClientSSL.java:148) and logging output for this testcase says about timeouts, (citing here, as Gump logs are overwritten on each run) [[[ 19-Oct-2015 06:35:19.939 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testBug56032] 19-Oct-2015 06:35:21.425 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["https-nio2-127.0.0.1-auto-1"] 19-Oct-2015 06:35:22.744 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Tomcat 19-Oct-2015 06:35:22.754 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/9.0.0-dev 19-Oct-2015 06:35:24.186 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["https-nio2-127.0.0.1-auto-1-41903"] 19-Oct-2015 06:35:36.587 WARNING [https-nio2-127.0.0.1-auto-1-exec-4] org.apache.tomcat.websocket.WsSession.onClose Failed to flush batched messages on session close java.net.SocketTimeoutException at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:295) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendMessageBlock(WsRemoteEndpointImplBase.java:256) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.flushBatch(WsRemoteEndpointImplBase.java:119) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.setBatchingAllowed(WsRemoteEndpointImplBase.java:106) at org.apache.tomcat.websocket.WsSession.onClose(WsSession.java:502) at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.close(WsHttpUpgradeHandler.java:230) at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:150) at org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:50) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:703) at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.run(Nio2Endpoint.java:1681) at org.apache.tomcat.util.net.Nio2Endpoint.processSocket0(Nio2Endpoint.java:407) at org.apache.tomcat.util.net.Nio2Endpoint.processSocket(Nio2Endpoint.java:391) at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$4.completed(Nio2Endpoint.java:700) at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$4.completed(Nio2Endpoint.java:678) at org.apache.tomcat.util.net.SecureNio2Channel$3.completed(SecureNio2Channel.java:823) at org.apache.tomcat.util.net.SecureNio2Channel$3.completed(SecureNio2Channel.java:778) at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126) at sun.nio.ch.Invoker$2.run(Invoker.java:218) at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) 19-Oct-2015 06:35:41.602 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["https-nio2-127.0.0.1-auto-1-41903"] 19-Oct-2015 06:35:41.601 INFO [https-nio2-127.0.0.1-auto-1-exec-4] org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.doClose Failed to close the ServletOutputStream connection cleanly java.io.IOException: Pending write, so remaining data in the network buffer, can't send SSL close message, force a close with close(true) instead at org.apache.tomcat.util.net.SecureNio2Channel.close(SecureNio2Channel.java:529) at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper.close(Nio2Endpoint.java:965) at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.doClose(WsRemoteEndpointImplServer.java:172) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.close(WsRemoteEndpointImplBase.java:698) at org.apache.tomcat.websocket.WsSession.sendCloseMessage(WsSession.java:577) at org.apache.tomcat.websocket.WsSession.onClose(WsSession.java:508) at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.close(WsHttpUpgradeHandler.java:230) at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:150) at org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:50) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:703) at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.run(Nio2Endpoint.java:1681) at org.apache.tomcat.util.net.Nio2Endpoint.processSocket0(Nio2Endpoint.java:407) at org.apache.tomcat.util.net.Nio2Endpoint.processSocket(Nio2Endpoint.java:391) at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$4.completed(Nio2Endpoint.java:700) at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$4.completed(Nio2Endpoint.java:678) at org.apache.tomcat.util.net.SecureNio2Channel$3.completed(SecureNio2Channel.java:823) at org.apache.tomcat.util.net.SecureNio2Channel$3.completed(SecureNio2Channel.java:778) at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126) at sun.nio.ch.Invoker$2.run(Invoker.java:218) at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Caused by: java.nio.channels.WritePendingException at sun.nio.ch.AsynchronousSocketChannelImpl.write(AsynchronousSocketChannelImpl.java:352) at sun.nio.ch.AsynchronousSocketChannelImpl.write(AsynchronousSocketChannelImpl.java:387) at org.apache.tomcat.util.net.SecureNio2Channel$FutureFlush.<init>(SecureNio2Channel.java:142) at org.apache.tomcat.util.net.SecureNio2Channel.flush(SecureNio2Channel.java:177) at org.apache.tomcat.util.net.SecureNio2Channel.close(SecureNio2Channel.java:523) ... 23 more 19-Oct-2015 06:35:41.608 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service Tomcat 19-Oct-2015 06:35:41.621 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["https-nio2-127.0.0.1-auto-1-41903"] 19-Oct-2015 06:35:41.622 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["https-nio2-127.0.0.1-auto-1-41903"] ]]] At Buildbot I see similar messages,but the test is not failing. So apparently the "cannot write" situation is expected, e.g. the client side of connection is closed. https://ci.apache.org/projects/tomcat/tomcat9/logs/logs/1709375/TEST-org.apache.tomcat.websocket.TestWebSocketFrameClientSSL.NIO.txt Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
