Nice! Much appreciated! --Alex
> -----Original Message----- > From: Chiradeep Vittal > Sent: Thursday, July 25, 2013 2:44 AM > To: dev@cloudstack.apache.org > Cc: Alex Huang > Subject: Re: CallContexts? > > Fixed > commit 1744ed7ad5b512135e567576271e11a6e26e4379 > > > Alex, please review. > > On 7/25/13 11:53 AM, "Chiradeep Vittal" <chiradeep.vit...@citrix.com> > wrote: > > >I can confirm this serious bug on master. > > > >On 7/18/13 1:55 PM, "Prasanna Santhanam" <t...@apache.org> wrote: > > > >>On Thu, Jul 18, 2013 at 11:58:30AM +0530, Prasanna Santhanam wrote: > >>> I see the following repeated lines with API calls on master code > >>> lately: What's the call context? and what's the role? > >>> > >>> 2013-07-18 11:52:24,372 DEBUG [cloudstack.context.CallContext] > >>>(RouterStatusMonitor-1:ctx-9bb138b4) Context removed > >>>CallContext[acct=1; user=1; > >>>session=9bb138b4-29c1-4ddf-ab47-9307a600d31e] > >>> > >>> * CallContext records information about the environment the call is > >>>made. This > >>> * class must be always be available in all CloudStack code. > >>> > >>> Does this mean we have to do something special when creating new > APIs? > >>>I'm not > >>> quite clear from this description. > >>> > >>It seems from the logs that all APIs are now getting the context as > >>user=1,account=1 (SYSTEM). Filed CLOUDSTACK-3626. > >> > >> > >> > >>-- > >>Prasanna., > >> > >>------------------------ > >>Powered by BigRock.com > >> > >
