[
https://issues.apache.org/jira/browse/DTACLOUD-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michal Fojtik resolved DTACLOUD-489.
------------------------------------
Resolution: Fixed
Assignee: Michal Fojtik
Jan's patch pushed:
Thanks!
commit 7313aed50933dd34266a26a8c0e5cf1dd8834b2c
Author: Jan Provaznik <[email protected]>
Date: Mon Feb 25 11:03:54 2013 +0100
If an exception is raised in a driver and the request is being processed by
"standard_index_operation" (most of index actions), then a user gets back
only not very descriptive "Internal server error" message. The exception
is not logged.
> More verbose reporting of internal server errors
> ------------------------------------------------
>
> Key: DTACLOUD-489
> URL: https://issues.apache.org/jira/browse/DTACLOUD-489
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Reporter: Jan Provaznik
> Assignee: Michal Fojtik
>
> If a backend error occurs when processing an index action, then the exception
> is replaced by general "Internal server error" message without any details.
> The error is not logged in deltacloud log too.
> The problem is that lib/deltacloud/helpers/deltacloud_helper.rb:filter_all
> sets 500 error code to all exceptions with missing error code, then
> report_error method replaces the original exception with new exception
> instance containing just the error code.
--
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
