-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ClassLoaderIClassLoader 's ClassNotFoundException handle mechanism enhancement #104
Comments
Are you able to share the reproducible case? I'm not sure it's a good idea to hide multiple upstream exceptions like this ... It could make debugging issues harder in the future |
The aim is to distinguish between „Class does not exist“ and „exception when loading the class“, when the JRE maps both cases to I‘ll change the code as requested (it is a good pattern to wrap exception X in another exception X in order to augment the message). |
I fixed it:
Please test! |
Thanks very much for this fix. I ran into this issue on a Spark cluster when using the old version and thought I would leave a stack trace so that people could find this issue more easily. Caused by: org.codehaus.commons.compiler.CompileException: Line 11, Column 21: FunctionUtils Caused by: java.lang.ClassNotFoundException: FunctionUtils |
in some osgi environment, the e.getException() will return a ClassNotFoundException too.
can we add an additional condition to handle above case?
The text was updated successfully, but these errors were encountered: