Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 6541 invoked from network); 15 Aug 2002 19:10:28 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 15 Aug 2002 19:10:28 -0000 Received: (qmail 24235 invoked by uid 97); 15 Aug 2002 19:09:43 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 24172 invoked by uid 97); 15 Aug 2002 19:09:42 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 24128 invoked by uid 98); 15 Aug 2002 19:09:41 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Subject: Testing session time-out behaviour To: "Tomcat Users List" X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: From: JEWeaver@thoughtworks.com Date: Thu, 15 Aug 2002 14:07:13 -0500 X-MIMETrack: Serialize by Router on Mother/ThoughtWorks.COM/US(Release 5.0.10 |March 22, 2002) at 08/15/2002 02:28:48 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, I have a web app with some specific requirements for session timeout. I would like to write automated acceptance tests to verify these requirements, and am faced with some options: - set web.xml to time-out in 1 minute, have my tests wait for just over a minute to force time-out - talk to my server (tomcat during testing) from the test client code (junit tests using httpunit) to somehow request it to time out - execute the shutdown / startup commands from the client code (session information for tomcat 4.0 goes away when i do this). I have a small app, so startup shutdown are both relatively quick (seconds). Waiting a minute is a pain, because I have to change web.xml and reset it, also because I have a lot of screens and behaviours to test (hence the desire to automate), so even setting down to a minute I expect it would take my automated test suite from what is now about 5 minutes to run to about 30 minutes. As far as communicating with tomcat goes, I tried doing a get on the manager urls to reload the app, also to stop followed by start - but this does not appear to cause it to lose the session information. As far as executing startup / shutdown batch files, the rub is waiting on the shutdown and startup to complete before proceeding with the test. It is proving to be extremely tricky to do. So, from a java test client, is there a supported and relatively easy way for me to get tomcat to drop a session in the middle of a test? Suggestions? j -- To unsubscribe, e-mail: For additional commands, e-mail: