https://issues.apache.org/bugzilla/show_bug.cgi?id=53871
--- Comment #12 from Mark Thomas <ma...@apache.org> --- The point here is that if you ship an application that does this: <quote> Due to dependency management problems I deployed a WAR file containing two JAR files containing different versions of a library, where version 1 contained a class A which inherited from B and another version 2 which contained a class B inheriting from A. The classes were loaded in such an order that A and B cyclically inherited from each other which leads to a stack overflow in populateSCIsForCacheEntry because it does not detect cycles in the inheritance tree. </quote> Then the application is going to fall over as soon as it hits those classes. That is an application bug, not a Tomcat bug. You might be lucky and not use those classes at all in your application. In which case you wouldn't see this until Tomcat was updated to scan classes for annotations as intended by the Servlet 3.0 EG. Hence it might look like a Tomcat problem. If you have a valid set of JARs that can trigger a stack overflow then that would be a new bug and one that would get fairly prompt attention. -- 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
