[Bug 63685] WebappClassLoaderBase and StandardRoot reload classes from jar files on each call of getResource, getResourceAsStream and etc. that hit application startup performance
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685 Mark Thomas changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Mark Thomas --- This issue has been open for more than a month waiting for a use case that requires the caching of class files. None has been provided so I am closing this as WONTFIX. Feel free to re-open this with an explanation of why this feature is required if you have such a use case -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63685] WebappClassLoaderBase and StandardRoot reload classes from jar files on each call of getResource, getResourceAsStream and etc. that hit application startup performance
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685 --- Comment #4 from Mark Thomas --- (In reply to Andrei Ivanov from comment #3) > I remember having a problem with AOP and load time weaving where Tomcat was > scanning the WAR for servlet annotations and caching the classes so by the > time the app was starting and LTW enabled, the classloader was returning the > cached classes instead of passing them through the instrumentation agent, That is a known issue with the Servlet spec: https://github.com/eclipse-ee4j/servlet-api/issues/79 This bug report is still waiting for a justification for caching the content of class files. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63685] WebappClassLoaderBase and StandardRoot reload classes from jar files on each call of getResource, getResourceAsStream and etc. that hit application startup performance
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685 --- Comment #3 from Andrei Ivanov --- I remember having a problem with AOP and load time weaving where Tomcat was scanning the WAR for servlet annotations and caching the classes so by the time the app was starting and LTW enabled, the classloader was returning the cached classes instead of passing them through the instrumentation agent, -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63685] WebappClassLoaderBase and StandardRoot reload classes from jar files on each call of getResource, getResourceAsStream and etc. that hit application startup performance
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685 --- Comment #2 from Mark Thomas --- Leaving this open for now but it will be closed as WONTFIX if no justification for caching classes is provided. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63685] WebappClassLoaderBase and StandardRoot reload classes from jar files on each call of getResource, getResourceAsStream and etc. that hit application startup performance
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685 Mark Thomas changed: What|Removed |Added Status|NEW |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63685] WebappClassLoaderBase and StandardRoot reload classes from jar files on each call of getResource, getResourceAsStream and etc. that hit application startup performance
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685 --- Comment #1 from Mark Thomas --- It is expected that a class file is read once and once only when the class is loaded into memory. Therefore there is no point caching the contents of a class file. What use case requires that classes are loaded as resource files rather than classes? If there is sufficient justification we can always add an option to cache class files. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63685] WebappClassLoaderBase and StandardRoot reload classes from jar files on each call of getResource, getResourceAsStream and etc. that hit application startup performance
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685 Alexandr changed: What|Removed |Added Hardware|All |PC -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 63685] WebappClassLoaderBase and StandardRoot reload classes from jar files on each call of getResource, getResourceAsStream and etc. that hit application startup performance
https://bz.apache.org/bugzilla/show_bug.cgi?id=63685 Alexandr changed: What|Removed |Added Severity|normal |major -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
