Github user steveloughran commented on the pull request:
https://github.com/apache/spark/pull/6033#issuecomment-100831678
Jetty would catch them and generate a 500 response with no body, and not
log it *as far as I could find*.
This patch catches and logs via the spark->log4j layer, and includes the
URL at fault in the diagnostics.
Something in the jetty stack is still stripping the text out of the
generated 500 responses (I tested and the payload does come through if you set
the response to 200, but that's no good for machine parsing. Ideally endpoints
should have a machine error code & messages for humans. That's why in Axis we
put a lot of effort [getting stack traces in to soap
faults|](https://axis.apache.org/axis/java/apiDocs/org/apache/axis/AxisFault.html).
this patch doesn't get any stack trace to the clients; that could be some
separate work for someone, which, after this patch, could just be turning off
some default handlers
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
