Revise r15383, activating a message priority of 6 is too much, the message will

not be retried in case of error. A priority of 3 is enough to give more chance
to activities like indexing to be executed before.



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

product/ERP5Type/RoleProviderBase.py

@@ -271,19 +271,19 @@ class RoleProviderBase:
       for i in xrange(0, object_list_len, 100):
         current_path_list = object_path_list[i:i+100]
         portal_activities.activate(activity='SQLQueue',
-                                   priority=6,
+                                   priority=3,
                                    tag=update_role_tag)\
               .callMethodOnObjectList(current_path_list,
                                       'updateLocalRolesOnSecurityGroups',
                                       reindex=False)
         portal_activities.activate(activity='SQLQueue',
-                                   priority=6,
+                                   priority=3,
                                    after_tag=update_role_tag)\
               .callMethodOnObjectList(current_path_list,
                                       'reindexObjectSecurity')
 
       if REQUEST is not None:
-        return self.manage_editRolesForm(REQUEST, 
+        return self.manage_editRolesForm(REQUEST,
                  manage_tabs_message='%d objects updated' % (object_list_len,))
 
 InitializeClass(RoleProviderBase)