Anonymous | Login | Signup for a new account | 04-27-2024 19:50 PDT |
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 | ||||
0003988 | [Resin] | minor | always | 04-08-10 09:25 | 09-08-14 17:26 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | no change required | ||||||
Status | closed | Product Version | |||||||
Summary | 0003988: memory leak detection enhancement | ||||||||
Description |
(rep by Daniel Lopez) I've come across a new feature that is to be implemented in Tomcat 6 to help detect/prevent/notifiy the too common OOME (permGen) problems and as we don't use Tomcat but do use Resin, I wondered if the Caucho guys have considered adding a similar mechanism to Resin. As the article points out, many people end up blaming the containter for such errors, as their application runs "fine", so I think it is in our best interest, container vendors included, to sort out who's to blame in this topic. Even if fixing is not always possible, it is not, simply notifiying that "web app classloader could not be recycled due to a leak in the application" would help and creating a list of libraries that cause these things might encourage library creators to be more careful. |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
There are no notes attached to this issue. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
30 total queries executed. 26 unique queries executed. |