Summary: | Memory leak in org.apache.taglibs.standard.lang.jstl.ELEvaluator | ||
---|---|---|---|
Product: | Taglibs | Reporter: | pmd1nh-rm |
Component: | Standard Taglib | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 1.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows Server 2003 | ||
Attachments: |
Snapshot shows large entries in the Map
standard.1.0.6 patched for j2se 1.4 snapshot of ELEvaluator direct children snapshot new ELEvaluator |
Description
pmd1nh-rm
2010-05-14 10:52:23 UTC
Hi, Are you sure apply correctly the patch? These patch is must be apply not in root path, also in \src\org\apache\taglibs\standard. And extra/collections package must be move to extra\commons\collections before running ant. (the patch is a little confusing). Could you attach a memory snapshot for all direct ELEvaluator childrens? Created attachment 25456 [details]
standard.1.0.6 patched for j2se 1.4
Attached the standard.jar with the patch
Created attachment 25458 [details]
snapshot of ELEvaluator direct children
Hi, Yes, I'm sure that the patch has been applied correctly. I have also downloaded your attachment of standard-1.0.6, decompiled, and compared with ours. They are same (from the main fixes in lang.jstl.ELEvaluator and Evaluator to the extra files in extra.commons.collections.*). I attached the snapshot of ELEvaluator's direct children Thanks! Hi again, I just have tested the jar and seems to work correctly. Sorry, but your jar seems not to be correctly. In your first snapshot you can see these: - ELEvaluator - Colletions -HashMap -.... lots of HashMap In my snapshot I attach today, yo can see: - ELEvaluator - Colletions -LRUMap - AbstractHasedMap - 79 AbstractLinkedMap So you are using the old ELEvaluator. Be sure your ELEvaluator are in: org\apache\taglibs\standard\lang\jstl and not in: standard\lang\jstl Or if you prefer, test my jar file. Created attachment 25461 [details]
snapshot new ELEvaluator
Hi, Can you please share the application/JSP source that you used to test this? I don't have a test case for this as the dump was sent in by one of our customers. Thank you for your help! Sorry, I dont have any test case. I tested it in our aplication. Noting that we just dropped the LRUMap code in trunk and replaced it with a JDK 1.5 class (LinkedHashMap). Looking at the comments, it looks as though the issue was resolved as a no-issue? Patch not applied on jar? If still an issue, retrying with trunk (JSTL 1.2) would be valuable. Let me know if you need a build uploaded. Hi, User's app overwrites our jar and causes this issue. Please close down this thread. Thank you very much for your help! Regards, Resolving as per comment 10 this appears to be a user issue |