These are 60min and 1440min for standard jobs and 600sec for vm related jobs right? I have tasks that are from dec 27 still in there.... and these are vm jobs.
FG On Jan 5, 2015 5:25 PM, "Motty Cruz" <motty.c...@gmail.com> wrote: > Francois, > you can change timeout default settings in "global settings", if you have > not done so. > > Thanks, > Motty > On 01/05/2015 02:09 PM, Francois Gaudreault wrote: > >> Yes. And also tons of job in the async_job table with status 0. >> >> FG >> >> On 2015-01-05 4:54 PM, ilya musayev wrote: >> >>> Do you see something along the lines of below? please provide the >>> complete error message. >>> >>> (1434,VmWorkJobQueue, 2471) is reaching concurrency limit 1 >>> (1475,VmWorkJobQueue, 2483) is reaching concurrency limit 1 >>> (1477,VmWorkJobQueue, 2484) is reaching concurrency limit 1 >>> (1478,VmWorkJobQueue, 596) is reaching concurrency limit 1 >>> (981,VmWorkJobQueue, 2371) is reaching concurrency limit 1 >>> >>> >>> On 1/5/15, 1:40 PM, Francois Gaudreault wrote: >>> >>>> Hi folks, >>>> >>>> What would be the best way to cancel jobs that are "stuck"? I was >>>> expecting them to timeout, but for some reasons they are not. >>>> >>>> Thanks. >>>> >>>> >>> >>> >>> >> >> >
