Anonymous | Login | Signup for a new account | 11-07-2024 18:27 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 | ||||
0002814 | [Resin] | minor | always | 07-01-08 12:29 | 08-07-08 14:35 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | urgent | Resolution | fixed | ||||||
Status | closed | Product Version | 3.0.26 | ||||||
Summary | 0002814: isapi_srun taking extra CPU on long-running process | ||||||||
Description |
(rep by Martin Weinig) I intended to mention the other issue we?re seeing that cropped up following the upgrade to 3.0.26: When we have a long running JSP or servlet, the w3wp.exe process consumes 100% of one CPU while waiting on the Resin process to finish its work. It appear to process normally for about 60 seconds and then w3wp starts burning cycles until the jsp finishes. I was able to reproduce the situation with the following simple JSP: <% java.util.Date d1 = new java.util.Date(); java.util.Date d2 = new java.util.Date(d1.getTime() + (1000*60*5)); while(d1.getTime() < d2.getTime()){ d1 = new java.util.Date(); } %> Done. |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
There are no notes attached to this issue. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
26 total queries executed. 24 unique queries executed. |