Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Later
-
0.19.0
-
None
-
None
Description
This is being added as a bugrep so that other people can find it, and the workaround
1. On my machine TestFileSystem will hang, even overnight -even though the build was set with a timeout.
2. halting the build left a JVM running; it was not being killed.
3. Under the IDE, the main thread appears hung in the native library call to get a stack trace, somewhere inside Log4J
4. the IDE could not halt the build, and could not be shut down cleanly either
The fix for this problem was to edit conf/log4j.properties and switch to a log4J log pattern that did not print the line of the code
log4j.appender.console.layout.ConversionPattern=%-4r %-5p %c %x - %m%n
Given that working out a stack trace can be an expensive call, and that it can apparently hang some JVMs, perhaps it should not be the default.