incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frank Zhang <Frank.Zh...@citrix.com>
Subject RE: Add ExceptionResponse in the log?
Date Mon, 09 Jul 2012 18:11:56 GMT
Vijay, please make sure stack trace is logged as well.  Text of Exception.getMessage() is definitely
not enough 

> -----Original Message-----
> From: Alena Prokharchyk [mailto:Alena.Prokharchyk@citrix.com]
> Sent: Monday, July 09, 2012 10:53 AM
> To: cloudstack-dev@incubator.apache.org; Vijayendra Bhamidipati
> Subject: Re: Add ExceptionResponse in the log?
> 
> We should def. print out the reason.
> 
> Vijay, just override toString() method in the Exception response to log the
> reason for the failure in addition to the error code.
> 
> -Alena.
> 
> 
> On 7/9/12 10:44 AM, "Sheng Yang" <sheng@yasker.org> wrote:
> 
> >After we add ExceptionResponse for user to better understand what's
> >wrong, there has been nothing left in the log for developer to know
> >what's wrong...
> >
> >What we got now is only something like:
> >
> >2012-07-09 19:22:10,098 DEBUG [cloud.async.AsyncJobManagerImpl]
> >(Job-Executor-32:job-29) Complete async job-29, jobStatus: 2,
> >resultCode: 530, result:
> >com.cloud.api.response.ExceptionResponse@3fa28ae
> >
> >And nothing else.
> >
> >Could we just output every ExceptionResponse in the log? That's would
> >be much more helpful.
> >
> >--Sheng
> >
> 


Mime
View raw message