[Bug 63038] When tomcat reads damaged zip dependencies, the tomcat does not write original reason of a problem.

2019-01-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63038

Mark Thomas  changed:

   What|Removed |Added

 OS||All
 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #2 from Mark Thomas  ---
The general approach in that part of the code base is to log the original
exception at debug level and throw a CNFE that names the class with the
problem.

I have fixed this issue using the standard approach.

Fixed in:
- trunk for 9.0.15 onwards
- 8.5.x for 8.5.38 onwards

Note that 7.0.x was not affected.

-- 
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 63038] When tomcat reads damaged zip dependencies, the tomcat does not write original reason of a problem.

2018-12-25 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=63038

--- Comment #1 from Vorvulev Sergey  ---
Created attachment 36350
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=36350=edit
try to read the
org/springframework/scheduling/config/TaskExecutorFactoryBean.class

-- 
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