findCause() only works using the cause property, whereas in many cases (older code typically that predates the cause property, introduced in JDK 1.4)) there's an alternate property that stores the actual nested exception.
ExceptionAnalyzer does it correctly, at higher cost (lots of property access to identify the cause).
|Field||Original Value||New Value|
|Assignee||Howard M. Lewis Ship [ hlship ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Fix Version/s||5.3 [ 12316024 ]|
|Resolution||Fixed [ 1 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|286d 20h 42m||1||Howard M. Lewis Ship||23/Sep/11 18:47|