[
https://issues.jboss.org/browse/AS7-813?page=com.atlassian.jira.plugin.sy...
]
Scott Marlow commented on AS7-813:
----------------------------------
I'm thinking specifically of places that catch exceptions already but aren't
logging the exception. Instead they throw a different exception that tries to describe
what went wrong.
My suggestion is to continue to log the detailed exceptions that aren't being thrown
to the higher level. When we have figured out a way to describe what went wrong, well
enough, then we could stop logging the originating exception details.
configuration option to show/hide system/user application exceptions
and possibly new api method for logging a system exception versus user application
exception
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: AS7-813
URL:
https://issues.jboss.org/browse/AS7-813
Project: Application Server 7
Issue Type: Feature Request
Components: Logging
Reporter: Scott Marlow
Assignee: Jason Greene
Priority: Minor
I would like to be able to show/hide system exception call stacks in the logs based on a
configuration option. The same for showing/hiding user application exception call
stacks.
To support the above configuration change, I would like to see a way to log a system
exception versus an user application exception.
By system exception, I mean any exception that is logged via a distinctive api method.
Perhaps something like:
log.systemError(String message, Throwable infrastructureException);
This would help reduce the time it takes to debug infrastructure issues (e.g. the NPE at
http://pastie.org/1917562 is well hidden which in itself is a bug).
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira