git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@37189 20353a03-c40f-0410-a6d1-a30d3c3de9de

Conflicts:
	bt5/erp5_base/bt/revision
	bt5/erp5_simulation/DocumentTemplateItem/InvoiceSimulationRule.py
	bt5/erp5_simulation/bt/revision
	bt5/erp5_trade/SkinTemplateItem/portal_skins/erp5_trade/Base_viewTradeFieldLibrary.xml
	bt5/erp5_trade/bt/change_log
	bt5/erp5_trade/bt/revision
	products/ERP5/Document/BusinessPath.py
	products/ERP5/Document/SimulationMovement.py
	products/ERP5/Document/TradeCondition.py
	products/ERP5/Document/TradeModelLine.py
	products/ERP5/bootstrap/erp5_mysql_innodb_catalog/bt/revision
	products/ERP5Type/ERP5Type.py

git-svn-id: https://svn.erp5.org/repos/public/erp5/sandbox/amount_generator@37129 20353a03-c40f-0410-a6d1-a30d3c3de9de

fixed by revision 35192 (wrong sql connector used by Id tool)

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@35197 20353a03-c40f-0410-a6d1-a30d3c3de9de

At most 1 message for a given serialization tag can be validated (cf [28706]).
Respect priority/date/uid when validating only 1 message (cf [34632]).

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@34841 20353a03-c40f-0410-a6d1-a30d3c3de9de

  -If an exception is raised when sending mail, the error is not lost
   (available in zope event.log)
  -If an exception is raised when using the site error logger, the error is not
   lost. This test passes for SQLDict, but fails if activity is SQLQueue
  -If a traceback could not be generated, a mail can still be sent


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@34819 20353a03-c40f-0410-a6d1-a30d3c3de9de

- When deleting duplicate messages, keep the one the highest score (priority,
  date, uid).
- When several messages have the same serialization_tag, always validate first
  the one with the highest score.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@34632 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@34303 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@33630 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@32882 20353a03-c40f-0410-a6d1-a30d3c3de9de

This test does more than test_6[89]_ so it replaces them.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@32881 20353a03-c40f-0410-a6d1-a30d3c3de9de

* Change subject from "Failed Processing Activity" to
  "Activity failed: <path>/<method>"
* The subject starts with "Pending activity already failed <failures> times:"
  if CMFActivity is going to reexecute indefinitely.
* Drop the first line of the body. It was repeating the the subject.
* Add number of failures.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@32880 20353a03-c40f-0410-a6d1-a30d3c3de9de

getActivityRuntimeEnvironment is changed to return an ActivityRuntimeEnvironment
instance instead of a dict (and this value is now stored in a transactional
variable, for automatic cleanup).
This object allow activities to change default behaviour of CMFActivity if an
error happens. In the future, this object could also allow executed activity to
inspect its related Message object.

In case of infinite retry, notify the user when the default limit is reached.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@32879 20353a03-c40f-0410-a6d1-a30d3c3de9de

Now, all messages can be executed 6 times by default (or more in case of
ConflictError), regardless their initial priority.
For compatibility reasons, the 'priority' column is still increased.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@32877 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@32876 20353a03-c40f-0410-a6d1-a30d3c3de9de

When a node is looking for activities to process, there's no point testing the
'processing' column. This fixes cases leaving activities at 'processing=1'
forever (unless, of course, a cluster is killed and restarted with fewer nodes).
Also remove now useless cleanup at startup.

One known case leaving such activities is when the first commit of
dequeueMessage raises, which can happen, for example, during migration of
portal_types.

It seems the 'processing' column becomes useless for CMFActivity.

Acked-by: Vincent Pelletier

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@32089 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@32088 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31892 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31888 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31846 20353a03-c40f-0410-a6d1-a30d3c3de9de

replace transaction subcommits (deprecated since Zope 2.8 or before) with optimistic savepoints, which do the same thing.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30370 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30232 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30029 20353a03-c40f-0410-a6d1-a30d3c3de9de

  for activity with group method_id and without group method_id

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28763 20353a03-c40f-0410-a6d1-a30d3c3de9de

Update CheckSerializationTag and check if serialization_tag blocks to validate the same tagged message and the message remains.
Split test_102_CheckSQLDictDoesNotDeleteDuplicatesBeforeExecution into two tests and covers new SQLDict behavior.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28739 20353a03-c40f-0410-a6d1-a30d3c3de9de

Rename test_102. The name said the test was checking SQLQueue feature, but the content was obviously checking SQLDict feature.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28738 20353a03-c40f-0410-a6d1-a30d3c3de9de

Fix a bug. serialization tag guarantees that tagged messages are processed serially and not parallelly.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28706 20353a03-c40f-0410-a6d1-a30d3c3de9de

Fix test_115_TestSerializationTagSQLDictPreventsParallelExecution. Delete remaining activities at the end. This broke other test.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28705 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28693 20353a03-c40f-0410-a6d1-a30d3c3de9de

- tests that no message are lost if we record more then MAX_MESSAGE_LIST_SIZE
  in one transaction.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28464 20353a03-c40f-0410-a6d1-a30d3c3de9de

activity table ( manageClearActivities ). Messages where always reactivated
using SQLDict


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27487 20353a03-c40f-0410-a6d1-a30d3c3de9de

Fix ActiveProcess.hasActivity. On active processes, hasActivity tests active_process_uid instead of path:
* hasActivity must handle the case when no document is provided (bug #1142)
* Fix initialisation of active_process_uid property on Message objects.
Add unit test.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27329 20353a03-c40f-0410-a6d1-a30d3c3de9de

any more in hasActivity


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26271 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26210 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@25336 20353a03-c40f-0410-a6d1-a30d3c3de9de

Implement ActiveProcess.hasActivity . It was present, but required data was never present in the table. Now that SQL{Dict|Queue}.hasActivity don't use "**kw" any more, it causes errors.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@25274 20353a03-c40f-0410-a6d1-a30d3c3de9de

Make all dtml tests use expr="...", so that tested values don't use acquisition. (Nice catch, Nicolas !)
Update callers to cope with those new limitations.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@25266 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@24992 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@24989 20353a03-c40f-0410-a6d1-a30d3c3de9de

  Add missing "global" declarations.
  Simplify: there is no need for both a global variable and a lock do just carry a boolean with atomic access.
  Add the possibility to put activity tool back in a working state after process_shutdown has been called.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@24988 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@24986 20353a03-c40f-0410-a6d1-a30d3c3de9de