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

  a lot performance under very high load
- add a round_robin_scheduling parameter for SQLQueue so that
  all messages on a same path will not be processed on the same
  node


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

Save last used processing node in a global variable. This avoids the case where all activities are assigned to first node when there is just one activity to distribute per distribute call.


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

Make possible to process more than one message per dequeueMessage call. This factorises MySQL access cost which is rather high because of a sort occuring in the query. SQLQueue_readMessage will still return just one message by default, so behaviour will not change unless default number of fetched rows is increased in that ZSQLMethod.


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

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

SQLQueue do not balances activities, it gives them all to a single node. So remove multi-node related code for cases where message is not marked as broadcast.


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

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

Abort a transaction synchronously, so that the status of connections and databases are updated after abort. This is a hack, but should work fine with all versions of Zope.

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

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

and fix some bugs.

The basic idea is to track a dependency graph to find executable
messages quickly. This makes the activity system far more efficient,
when you have many inter-dependent messages queued in the tables.

Also, this obsoletes the time shifting in the schedulers,
as executable messages can be found in a more efficient manner.
So the activity parameter "at_date" should work expectedly.

Now the API of validate methods in Activities return a
list of message objects instead of a boolean value. Such
a list contains messages that are depended upon by a given
message.

The validate method in Message accepts a new optional
parameter, check_order_validation, to indicate whether
order validation should be performed. The default behavior
has not changed.

getDependentMessageList is added to ActivityTool, Queue
and Message. This method collects dependent message for
a given message from all activities.

There are some other subtle changes. Look at the diffs for
more details.


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

Use portal_ids to generate message uids instead of using MySQL AUTO_INCREMENT. This will lower deadlock probability by removing the one caused by AUTO_INCREMENT table-level lock.


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

Do not delay or set to an error if an exception is raised in dequeueMessage, because invoke or invokeGroup should never emit an exception, so an exception should be nothing with a message itself.

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

class, now we have the exception instance, so use isinstance instead of
issubclass



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

store the exception in a variable to make sure we have the right one.



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

TypeError: LOG() got an unexpected keyword argument 'e'


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

be put in INVOKE_ERROR_STATE, but we will LOG a traceback (maybe we should
also call notifyUser).
remove the obsolete comment "what happens if read conflict error restarts
transaction", because this is handled explicitly here.



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

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

  deleting messages wich were not VALID, without execution !!
- Wrote a test to show that the bug is currently fixed.


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

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

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

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

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

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

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

put the message into an error state immediately.


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

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

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

Remove .cvsignore.
Repair broken image.


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

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

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

not being currently processed when starting zope, or they will be kept as
zombies in the SQL tables, blokcing other activities using after_method_id.


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

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

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

Now VALIDATION_ERROR_DELAY is in seconds but not in days.
timeShift is performed only for objects assigned to a given node.
SQLDict postpones all active objects which have the same order validation
specification at a time.


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

Add a tagging facility into SQLDict and SQLQueue. This changes also adds a new way of passing parameters by using _v_activate_kw. Look at the unit test for how to use it.


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

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

Added after_path_and_method_id


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

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

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

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