https://issues.apache.org/bugzilla/show_bug.cgi?id=57367
Bug ID: 57367
Summary: If JAR scan experiences a stack overflow, give the URL
from which each class in the loop was loaded in the
complaint
Product: Tomcat 7
Version: 7.0.57
Hardware: PC
Status: NEW
Severity: enhancement
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: eddie.k...@gmail.com
Created attachment 32304
--> https://issues.apache.org/bugzilla/attachment.cgi?id=32304&action=edit
Proposed patch that implements the feature enhancement
When you get a class loop that causes a stack overflow exception in JAR
scanning, the class names are currently listed, but not the location from which
each class was loaded. If a class is unexpectedly found in more than one
location (which will often be the source of this problem), then one has to
search every possible JAR to figure out the root cause.
It would really help understand these problems if the location from which each
class was loaded was included in the error report.
I will attach a proposed patch that adds this.
--
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
