Sanjay,
Thank you for the clarfication. I have created a ticket CLOUDSTACK-5410 to
track this one.

Saurav


On Sat, Dec 7, 2013 at 3:03 PM, Sanjay Tripathi
<sanjay.tripa...@citrix.com>wrote:

>  Hi Saurav,
>
>
>
> After the CS got switched to use new jobs framework, the
> AsyncJobManagerImpl.java file got moved under framework package; but the
> changes which I committed are not there in the file, somebody must have
> missed it during the transition.
>
>
>
> I’ll port the same changes in the new jobs framework, so that we can have
> UUIDs in our logs. Can you please open a ticket to track this issue.
>
>
>
> --Sanjay
>
>
>
> *From:* Saurav Lahiri [mailto:saurav.lah...@sungard.com]
> *Sent:* Thursday, December 5, 2013 3:53 PM
> *To:* dev@cloudstack.apache.org; Sanjay Tripathi
> *Subject:* [HELP] query w.r.t to cloudstack-1047
>
>
>
> Hi Sanjay,
>
> I was looking at the changes that were done as part of [cloudstack-1047 -
> tracking in logs using job id ]. From the defect history it appears that
> the change corresponded to
>
> setting job-<id>=[<uuid>].
>
>
>
> Currently the changes dont appear to be there in the master in
> the 
> ./framework/jobs/src/org/apache/cloudstack/framework/jobs/impl/AsyncJobManagerImpl.java
> file. Could you please let me know what I am missing here. This is to help
> me in identifying the best approach to fix cloudstack-3471.
>
>
>
> Thanks in advance.
>
>
>
> Saurav
>

Reply via email to