2014-07-11 0:53 GMT+04:00 Felix Schumacher <felix.schumac...@internetallee.de>: > > > On 10. Juli 2014 10:13:17 MESZ, Konstantin Kolinko <knst.koli...@gmail.com> > wrote: >>2014-07-10 7:02 GMT+04: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-bio has an issue affecting its community >>integration. >>> This issue affects 1 projects, >>> and has been outstanding for 6 runs. >>> The current state of this project is 'Failed', with reason 'Build >>Failed'. >>> For reference only, the following projects are affected by this: >>> - tomcat-trunk-test-bio : Tomcat 8.x, a web server implementing >>the Java Servlet 3.1, >>> ... >>> >>> >>> Full details are available at: >>> >>http://vmgump.apache.org/gump/public/tomcat-trunk/tomcat-trunk-test-bio/index.html >>> >> >>Test org.apache.catalina.session.TestPersistentManager FAILED >> >>[[[ >>Testsuite: org.apache.catalina.session.TestPersistentManager >>Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.868 >>sec >>------------- Standard Error ----------------- >>10-Jul-2014 02:51:45.769 INFO [main] >>org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler >>["http-bio-127.0.0.1-auto-1"] >>10-Jul-2014 02:51:45.811 INFO [main] >>org.apache.catalina.core.StandardService.startInternal Starting >>service Tomcat >>10-Jul-2014 02:51:45.822 INFO [main] >>org.apache.catalina.core.StandardEngine.startInternal Starting Servlet >>Engine: Apache Tomcat/8.0.10-dev >>10-Jul-2014 02:51:46.116 INFO [main] >>org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler >>["http-bio-127.0.0.1-auto-1-45846"] >>10-Jul-2014 02:51:47.503 INFO [main] >>org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler >>["http-bio-127.0.0.1-auto-1-45846"] >>10-Jul-2014 02:51:47.505 INFO [main] >>org.apache.catalina.core.StandardService.stopInternal Stopping service >>Tomcat >>10-Jul-2014 02:51:47.526 INFO [main] >>org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler >>["http-bio-127.0.0.1-auto-1-45846"] >>10-Jul-2014 02:51:47.527 INFO [main] >>org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler >>["http-bio-127.0.0.1-auto-1-45846"] >>------------- ---------------- --------------- >> >>Testcase: backsUpOnce took 2.848 sec >>FAILED >>expected:<[4AC2976017F91624B46E2D7D78F6ABE8]> but was:<[]> >>junit.framework.AssertionFailedError: >>expected:<[4AC2976017F91624B46E2D7D78F6ABE8]> but was:<[]> >>at >>org.apache.catalina.session.TestPersistentManager.backsUpOnce(TestPersistentManager.java:88) >>]]] > We might have to bump up the sleep time a little bit (one second now). > PersistentManager will save the session only if it seems to be older than one > second. >
For a record: The cause for that behaviour was that there was a race condition between a) Thread.sleep(1000) call in test b) Request.recycle() -> session.endAccess() call in Tomcat that processed the HTTP request If b) occurred later than a) then after the sleep() call the idle time of the session was less than one second. Thus the session was not eligible to be written out by PersistenceManager. I fixed this in r1609924 by waiting until session activity counter reaches zero. (TestPersistentManager.waitWhileSessionIsActive() method). Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
