Write a log message when findClass IOException is caught #4062
+2
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit just adds a simple
LOG.debug
message to output the contents of anIOException
that might be caught by the JRubyClassLoader during afindClass
call. We were encountering theIOException
in cases where our process ran out of file descriptors, leading theclassUrl.openStream
call to fail. This manifested in our application as aNoClassDefFoundError
downstream but because theIOException
is swallowed higher up, it was initially hard for us to able to determine what the root cause was. Being able to see this new debug message in the log output would significantly help with our ability to diagnose this kind of problem.