[teiid-issues] [JBoss JIRA] (TEIID-3911) Nearly all odata4 errors reported as internal server errors

[Steven Hawkins (JIRA)]

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

Steven Hawkins commented on TEIID-3911:
---------------------------------------

So without the changes you are suggesting that we convert all of our exceptions to writeError and add a server side log there as well?  Then the only thing would be to handled unchecked exceptions from us and exceptions from the OData framework itself (for example if we provide an incompatible value, then olingo effectively swallows the SerializerException on the server side).

With the changes it would still probably be good to have a general catch (Exception ) to ensure that a proper message is sent to the client even with unchecked exceptions.



> Nearly all odata4 errors reported as internal server errors
> -----------------------------------------------------------
>
>                 Key: TEIID-3911
>                 URL: https://issues.jboss.org/browse/TEIID-3911
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: OData
>    Affects Versions: 8.12
>            Reporter: Steven Hawkins
>             Fix For: 9.0
>
>
> From the TeiidServiceHandler we generally rethrow our exceptions as ODataApplicationExceptions that have a status code of 500 - however even using a different status code still results in a 500 error as the Olingo framework expects exception subclasses to be used (see ErrorHandler.handleException - a general application exception is always a 500 error).



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)