| Summary: | Minor glitch with display of negative TTL on sessionDetail.jsp | ||
|---|---|---|---|
| Product: | Tomcat 6 | Reporter: | Konstantin Kolinko <knst.kolinko> |
| Component: | Manager application | Assignee: | Tomcat Developers Mailing List <dev> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | ||
| Priority: | P2 | ||
| Version: | 6.0.29 | ||
| Target Milestone: | default | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Attachments: | sessionDetail.jpg - screenshot | ||
Fixed in trunk in r1037887 (will be in 7.0.5), proposed for 6.0 Konstantin, you've mentioned the problem, that sessions with negative TTL are still alive after a Tomcat restart. I can't find a bug report. Is this problem fixed, too? Christian |
Created attachment 26331 [details] sessionDetail.jpg - screenshot To reproduce 1. Start Tomcat 2. Create a session 3. Stop Tomcat. Wait for more than TTL (default: 30 minutes). Start Tomcat. 4. Go to the Manager web application and look at the Session Details page for the session. I had some instance of 6.0.29 lying on my drive for several months. The TTL value was printed as "0-2982:0-20:0-59" instead of "-2982:20:59". I am attaching the screenshot. I wonder why the session was still alive, but that is a different question. The bug is in JspHelper.secondsToTimeString(), as it does not deal with negative values.