if a error happen in ActivityTool.invoke or around, the message will immediatly

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

product/CMFActivity/Activity/SQLDict.py

@@ -326,6 +326,8 @@ class SQLDict(RAMDict):
             if len(uid_list):
               activity_tool.SQLDict_assignMessage(uid = uid_list, 
                                                   processing_node = INVOKE_ERROR_STATE)
+              LOG('SQLDict', WARNING, 'Error in ActivityTool.invoke', e=sys.exc_info())
+
         get_transaction().commit()
         return 0
 

product/CMFActivity/Activity/SQLQueue.py

@@ -122,7 +122,7 @@ class SQLQueue(RAMQueue):
           return 0
 
         # Try to invoke
-        activity_tool.invoke(m) # Try to invoke the message - what happens if read conflict error restarts transaction ?
+        activity_tool.invoke(m) # Try to invoke the message
         if m.is_executed:                                          # Make sure message could be invoked
           get_transaction().commit()                                        # If successful, commit
       except:
@@ -142,6 +142,8 @@ class SQLQueue(RAMQueue):
           # For the other exceptions, put it into an error state.
           activity_tool.SQLQueue_assignMessage(uid = line.uid, 
                                                processing_node = INVOKE_ERROR_STATE)
+          LOG('SQLQueue', WARNING, 'Error in ActivityTool.invoke', e=sys.exc_info())
+
         get_transaction().commit()
         return 0