Neverending loop triggered in org.mortbay.log.Log.unwind

org.mortbay.log.Log.unwind attempts to walk the chain of exception causes using reflection to determine whether the current exception implements one of four cause accessors. By sheer dumb luck, our application just happened to implement some custom logic in a getRootCause method that may return this. E.g., our implementation of the method walks the chain of causes to return the base cause which may well be the exception itself if it has no cause.

Log.unwind has no validation logic to make sure that th2 != th, causing Jetty to enter a neverending loop, resulting in a stack overflow.