2012/1/10 Konstantin Kolinko <knst.koli...@gmail.com>: > 2012/1/9 Konstantin Kolinko <knst.koli...@gmail.com>: >>>> 2012/1/7 Rainer Jung <rainer.j...@kippdata.de>: >>>>> >>>>> Maybe enable the accesslog during testing with test.accesslog=true, so one >>>>> can check after the next failure whether the contents agree with your >>>>> assumption. Not sure, whether Gump offers access to the access log for >>>>> checking. >>>> >> >> I updated Gump configuration for tc7 and trunk enabling the access >> log. We will see how it goes with next run. >> > > So Gump runs with access logs. Look for "access_log.yyyy-mm-dd" in the > list of files. > > (...)
Last run of tomcat-tc7.0.x-test failed with org.apache.catalina.mbeans.TestRegistration.BIO.txt: [[[ Testcase: testMBeanDeregistration took 1.756 sec FAILED Remaining: [Tomcat:type=RequestProcessor,worker="http-bio-127.0.0.1-auto-1",name=HttpRequest1] expected:<0> but was:<1> junit.framework.AssertionFailedError: Remaining: [Tomcat:type=RequestProcessor,worker="http-bio-127.0.0.1-auto-1",name=HttpRequest1] expected:<0> but was:<1> at org.apache.catalina.mbeans.TestRegistration.testMBeanDeregistration(TestRegistration.java:209) ]]] The TestRegistration.BIO test did run from Jan 10, 2012 3:16:55 AM till Jan 10, 2012 3:16:56 AM. There is noting wrong showing in access log: [[[ 127.0.0.1 - - [10/Jan/2012:03:16:50 +0000] "GET /test/annotatedServlet HTTP/1.1" 200 42 http-bio-127.0.0.1-auto-2-exec-2 2 127.0.0.1 - - [10/Jan/2012:03:16:55 +0000] "GET / HTTP/1.1" 200 - http-bio-127.0.0.1-auto-1-exec-1 83 127.0.0.1 - - [10/Jan/2012:03:17:02 +0000] "GET /examples/WEB-INF/doesntexistanywhere HTTP/1.1" 404 960 http-bio-127.0.0.1-auto-1-exec-2 8 ]]] The test that run before it, TestWebappClassLoaderMemoryLeak.BIO is here: [1] http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-test/gump_file/TEST-org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak.BIO.txt.html What is suspicious in [1] is this message: [[[ Jan 10, 2012 3:16:56 AM org.apache.catalina.util.LifecycleBase stop INFO: The stop() method was called on component [StandardEngine[Tomcat].StandardHost[localhost].StandardContext[]] after stop() had already been called. The second call will be ignored. ]]] but NIO run of TestWebappClassLoaderMemoryLeak has that message as well, but there were no problems in TestRegistration. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org