Commit 07ad763a authored by Sebastien Robin's avatar Sebastien Robin

- found a possible way where a message was processed but a

  failure occured a commit time. So this ended by deleted
  a message wich was not really processed because not commited.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@17815 20353a03-c40f-0410-a6d1-a30d3c3de9de
parent efe1e4fd
...@@ -268,6 +268,10 @@ class SQLQueue(RAMQueue, SQLBase): ...@@ -268,6 +268,10 @@ class SQLQueue(RAMQueue, SQLBase):
# same "try" block. # same "try" block.
get_transaction().commit() get_transaction().commit()
except: except:
# We must make sure that the message is not set as executed.
# It is possible that the message is executed but the commit
# of the transaction fails
value[1].is_executed = 0
LOG('SQLQueue', WARNING, 'Exception raised when invoking message (uid, path, method_id) %r' % (value, ), error=sys.exc_info()) LOG('SQLQueue', WARNING, 'Exception raised when invoking message (uid, path, method_id) %r' % (value, ), error=sys.exc_info())
try: try:
makeMessageListAvailable([value[0]]) makeMessageListAvailable([value[0]])
......
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 to comment