[overlord-issues] [JBoss JIRA] (SRAMP-129) Be more selective about what errors get logged by the server

[Eric Wittmann (JIRA)]

    [ https://issues.jboss.org/browse/SRAMP-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742442#comment-12742442 ] 

Eric Wittmann commented on SRAMP-129:
-------------------------------------

(09:39:14 AM) eric.wittmann at gmail.com/0DCF6CCB: So it's just a question of which exceptions get logged and which don't?
(09:39:52 AM) eric.wittmann at gmail.com/0DCF6CCB: If so, doesn't that come down to a case-by-case judgement call?
(09:40:03 AM) Kurt Stam: y - server errors should get logged on the server, user/client errors are 'normal' processing for the server and should not get logged on the server
(09:40:22 AM) Kurt Stam: yes it is a judgement call, which only you and I can make
(09:40:27 AM) eric.wittmann at gmail.com/0DCF6CCB: lol
(09:40:33 AM) Kurt Stam: (not the administrator of the server)
(09:40:36 AM) eric.wittmann at gmail.com/0DCF6CCB: sure
(09:40:43 AM) Kurt Stam: so we need to filter out what we log
(09:40:50 AM) Kurt Stam: so he can do his job
(09:41:33 AM) eric.wittmann at gmail.com/0DCF6CCB: so it sounds like we need an Exception hierarchy - so we can determine which ones are hard server errors and which ones are "user" errors (invalid query syntax, uuid not found, etc)
(09:41:34 AM) eric.wittmann at gmail.com/0DCF6CCB: yes?
(09:41:47 AM) Kurt Stam: yes
(09:41:49 AM) Kurt Stam: we do
(09:41:54 AM) eric.wittmann at gmail.com/0DCF6CCB: ok
                
> Be more selective about what errors get logged by the server
> ------------------------------------------------------------
>
>                 Key: SRAMP-129
>                 URL: https://issues.jboss.org/browse/SRAMP-129
>             Project: S-RAMP
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Kurt Stam
>            Assignee: Eric Wittmann
>             Fix For: Milestone 3 (Workflow and Relationships)
>
>
> There are a few stacktraces when running the test. We should change our code to make sure we don't show stack traces if there is no true exception.
> In general, this means we should be able to tell the difference between a hard server error (ioexception, modeshape blew up exception, etc) and a "user" error (invalid s-ramp query syntax, uuid not found, etc).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira