[teiid-issues] [JBoss JIRA] Created: (TEIID-386) Improve error reporting to NOT include stack traces when appropriate and logging level < Detail
Paul Nittel (JIRA)
jira-events at lists.jboss.org
Thu Feb 26 14:19:44 EST 2009
Improve error reporting to NOT include stack traces when appropriate and logging level < Detail
-----------------------------------------------------------------------------------------------
Key: TEIID-386
URL: https://jira.jboss.org/jira/browse/TEIID-386
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Environment: Any and all
Reporter: Paul Nittel
Assignee: Steven Hawkins
The server presently adds stack traces with reckless abandon. It seems like anything that upsets the software yields at least one stack trace.
I'd like to propose that "human errors", like parsing SQL statements, return just an error (in the logs, too). If the server is set to log at Detail or Trace, then crank out the stack traces if that's necessary. Logs that show only important stuff are more valuable.
(I looked in Teiid and didn't see an entry like this. If it's a dup, that's fine, as long as the stack trace deluge is remedied.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the teiid-issues
mailing list