Summary: | Processing spike when nesting a <c:url> in a <c:forEach> in a <c:if> | ||
---|---|---|---|
Product: | Taglibs | Reporter: | Chad Johnson <chadj> |
Component: | Standard Taglib | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Attachments: | Testcase from Chad Johnson |
Description
Chad Johnson
2002-07-31 13:56:59 UTC
Created attachment 2545 [details]
Testcase from Chad Johnson
Some clarifications: 1.) I tested this using version 1.0.1 2.) By "gets hits very often" I mean vigoursly hitting the reload button in a browser. 3.) The cpu spike and memory increase show themselves once all page requests have been answered. So that leads me to think that both aren't due to regular page processing. Could not reproduce the problem. Closing the bug for now. If you still feel there is a problem, please reopen with additional details and/or different sample code. To add some closure: When I was seeing this problem I was using a beta version of the 3.x Mysql driver (converting a ResultSet to a Result, then iterating over that with forEach). After upgrading to a stable version this problem went away. To clarify: "stable version" of the Mysql 3.x series Mysql driver |