[
https://issues.apache.org/jira/browse/QPID-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947350#comment-15947350
]
Keith Wall commented on QPID-7719:
----------------------------------
I can't reproduce this on trunk. Where do you see it? Uncaught exceptions
(RuntimeExceptions) are bubbling back into Jetty and Jetty is sending a 500.
The only time when this can't happen is if the response is already partially
written, in which case the response code will have already gone.
> [Java Broker] Set response code to 500 when unexpected error occurs during
> REST call
> -------------------------------------------------------------------------------------
>
> Key: QPID-7719
> URL: https://issues.apache.org/jira/browse/QPID-7719
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Lorenz Quack
>
> Currently if there is an unhandled exception in the REST layer we do not set
> a error response code. The servlet ends up returning 200 which is clearly
> incorrect.
> we should set the error code to 500 and ideally return a JSON error message.
> The code in question is the final {{else}} block in
> {{RestServlet#setResponseStatus}} (~line 960).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
