Unfortunately such traces too often don't contain much useful information at all. The proper procedure would be to catch the exceptions and annotate it with som

Unfortunately such traces too often don't contain much useful information at all. The proper procedure would be to catch the exceptions and annotate it with something useful like 'Config file /etc/foo/bar not found'. From the Admin POV that's more helpful than a 200 line pamphlet boiling down to something like 'AbstractConfigFactory: nullPointerException'.