Commit 0a66e514 by Ivan Tyagov

Default ERP5 instanciation uses following schema for naming all zope nodes:

  <family_name>-0..9 when number of nodes <= 10
  <family_name>-01..09 (or n) when number of nodes > 10

In scalability tests instance keeps track of old used nodes and when nodes > 10
will pick by default sort "activity-0" which is NO longer an existing zope process.
This is an ugly fix and real woraround is to have something like activities-000x schema by default
parent a3c40d0b
......@@ -20,6 +20,15 @@ if distribution_node_list:
if distribution_node is None:
distribution_node = activity_node_list[0]
# default ERP5 instanciation uses following schema for naming all zope nodes
# activities-0..9 when number of nodes <= 10
# activites-01..09 (or n) when number of nodes > 10
# in scalability tests instance keeps track of old used nodes and when nodes > 10
# will pick by default sort "activity-0" which is NO longer an existing zope process
# this is an ugly fix and real woraround is to have something like activities-000x schema by default
if distribution_node == "activities-0" and "activities-00" in activity_node_list:
# give precedence
distribution_node = "activities-00"
context.portal_activities.manage_addToProcessingList(activity_node_list)
context.portal_activities.manage_setDistributingNode(distribution_node)
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or sign in to comment