c2c-oerpscenario team mailing list archive

[Nicolas Bessi - Camptocamp <715418@xxxxxxxxxxxxxxxxxx>]

The problem is that it will not be possible to have multiple launch of
simultaneous cron in actual version of cron are they are not really
threaded. Only the "master cron is threaded".

C2c_cron_audittrail propose threaded concurrent cron be the way it
ensure uniqueness of cron is based on model/function instead of cron id
is too limitative. This will not allows to have same cron running with
different args. An other point is that is also right in the remarks of
Gerhard is that neither OpenERP base cron management or
c2c_cron_audittrail allows to have the same cron that can be
concurrently run. This is a useful feature.

We should link this bug on expert-framework mailinglist

Nicolas

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/715418

Title:
  [5.x] ir.cron - simultaneous start of  cron jobs

Status in OpenERP Server:
  New

Bug description:
  We have not checked if this is fixed in v6

  Batch-jobs defined via ir_cron may be started simultaneously/concurrently.
  (We have seen up to 17 identical executions of the same job)

  /base/ir/ir_cron.py starts timer (via netsvc.startTimer) without 
  checking, whether there is already a timer started for the same point in 
  time (or: without removing such simultaneous timers).
  Hence, ir_cron._poolJobs will be invoked several times simultaneously.

  I suggest to maintain a list of timers in /base/ir/ir_cron.py which 
  inhibits duplicate timers.
  Alternatively "duplicate" timers could be removed - although this might 
  be difficult to implement.
  Such a mechanism could also be implemented within netsvc.startTimer - on 
  the other hand: simultaneous jobs can also be useful (outside ir_cron).

  When are jobs "simultaneous"?
  I suggest to implement a "time-granularity" which is less or equal the 
  smallest granularity of ir_cron-Jobs, i.e. "minutes".
  To be on the safe side for long-running jobs, the time-granularity may 
  also be the shortest interval currently defined via ir_cron (e.g. 10 
  minutes).

  any ideas ?