[teiid-issues] [JBoss JIRA] Closed: (TEIID-386) Improve error reporting to NOT include stack traces when appropriate and logging level < Detail

Mon Mar 30 17:00:22 EDT 2009

     [ https://jira.jboss.org/jira/browse/TEIID-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins closed TEIID-386.
--------------------------------

    Resolution: Done

Changed the serverworkitem and requestworkitem to log processing exceptions with only the key information, but the full stack trace at the detail level.

> 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: Common
>    Affects Versions: 6.0.0
>         Environment: Any and all
>            Reporter: Paul Nittel
>            Assignee: Steven Hawkins
>            Priority: Minor
>             Fix For: 6.1.0
>
>
> 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