Anonymous | Login | Signup for a new account | 12-17-2024 08:33 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0000279 | [Resin] | minor | always | 06-20-05 00:00 | 01-26-06 15:23 | ||||
Reporter | user241 | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | |||||||
Summary | 0000279: proxy caching for included jsp's doesn't always work | ||||||||
Description |
RSN-314 i am not sure how provide evidence of this problem other than giving you are entire web application. essentially, for some reason, certain jsps do not get cached by resin. these files are being generated called as includes, eg: request.getRequestDispatcher(includeURI).include(request, response); the pattern is hard to nail down, except that: 1. generally, small jsps always get cached. the same file/jsp that has a larger size (eg. more records on the screen) will not get cached, but there is no fixed size where things stop getting cached - it seems to be dependent upon the particular jsp. 2. the complexity of the page seems to make a difference - a very large page that is just a dump of html will get cached (into the megabytes), whereas a smaller page (say 15k) that has lots of java scriplets, etc in it won't get cached. i have tried the cache max-entry-size parameter to no avail. (what is it's default anyways??). it seems like something in the processing of a jsp is causing the page to marked as 'dirty' or non-cacheable or something. in resin 2.x, all of my included jsp's get cached as expected and behave correctly. christian |
||||||||
Additional Information | 3.x pro. | ||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
42 total queries executed. 31 unique queries executed. |