I'd be inclined to keep it at INFO, to help in the following scenario: A user encounters some intermittent concurrency bug involving the classloader system, and submits a console log. A developer now reads through the JarClassLoader source, encounters the ClosedByInterruptException-related code, and thinks--"gee, I wonder if this code is somehow related to the bug I'm investigating". If the log message is left at INFO, and the console log does not contain the message, the developer knows they can safely ignore the ClosedByInterruptException-related code, and that the bug is somewhere else. If we don't print the log message by default, the developer may spend lots of time trying to exercise this odd code path to see if it's related to whatever bug they are investigating.
The event should be rare, and when it does happen, it would be unlikely to happen more than once in a given JVM session (since the class does get loaded in the end). Though if you want, I could reword the log message to emphasize the fact that it's really not an error. [ Full content available at: https://github.com/apache/incubator-netbeans/pull/854 ] This message was relayed via gitbox.apache.org for [email protected]
