topic Re: Suspend operation failed in Alfresco Archive

Suspend operation failed

rainman — Fri, 31 Aug 2012 02:46:52 GMT

Hi, allI was to suspend an process instance during the execution of a asynchronous service task, but the engine report the following exception: ExecutionEntity was updated by another transaction concurrently.I debugged the engine, and find that the SuspendProcessInstanceCmd and the Execu

Re: Suspend operation failed

ronald_van_kuij — Sat, 01 Sep 2012 14:14:14 GMT

Won't this already work if you have a transaction managed outside the engine? E.g. Using a jta transactionmanager? There will be no commit then in each command executed and thus no clashes?

Re: Suspend operation failed

rainman — Mon, 03 Sep 2012 00:58:53 GMT

Thanks for your reply

Re: Suspend operation failed

rainman — Mon, 03 Sep 2012 02:34:58 GMT

Won't this already work if you have a transaction managed outside the engine? E.g. Using a jta transactionmanager? There will be no commit then in each command executed and thus no clashes?

Sir, did you mean use "JtaProcessEngineConfiguration"?

Re: Suspend operation failed

meyerd — Mon, 03 Sep 2012 09:44:29 GMT

In your service task:

Context.getCommandContext()
   .execute(new SuspendProcessInstanceCmd(…));

this allows you to combine both commands into a single command context.

–

Wat Ronald suggests is that if you use a thread-aware transaction and connection propagation mechanism like JTA or Spring transactions, the "inner" command will not open a new DB connection but reuse the connection already obtained by the "outer" command, since it is bound to the thread.