topic Re: Timeout trying to lock table 'ACT_HI_ACTINST' [50200-132] in Alfresco Archive

Timeout trying to lock table 'ACT_HI_ACTINST' [50200-132]

ronnie_and_sand — Thu, 01 Dec 2011 21:56:38 GMT

Apologies again for having to include logs and scripts in-line. All attachment extensions I've tried are not allowed.We are looking at how Activiti handles process failure.The contrived script, below, throws an exception on the 2nd task.Immediate attempts to go to the Manage link in activiti-explore

Re: Timeout trying to lock table 'ACT_HI_ACTINST' [50200-132]

trademak — Fri, 02 Dec 2011 09:00:50 GMT

Hi,

Can you explain a bit more in detail what you are trying to proof with this and exactly when does this error occur.
So does it occur when you are starting multiple instances of this process while accessing the manage section in the Activiti Explorer?

Best regards,

Re: Timeout trying to lock table 'ACT_HI_ACTINST' [50200-132]

ronnie_and_sand — Fri, 02 Dec 2011 15:22:22 GMT

Our team was wondering how any of the products we are evaluating handle process exceptions.

This has generally occurred after starting just 1 instance of the process, followed by attempts to access the manage section of Activiti Explorer.

It looks like a best practice approach for our team will be to use BPMN exception handling, as hinted at here http://forums.activiti.org/en/viewtopic.php?f=6&t=2935 and described in the user manual.

Thanks!

Re: Timeout trying to lock table 'ACT_HI_ACTINST' [50200-132]

ronnie_and_sand — Fri, 02 Dec 2011 19:39:27 GMT

Here is a BPMN way to handle java exceptions.

A scriptTask template would be

        <scriptTask id="scriptTask1" name="scriptTask1" scriptFormat="groovy">
            <script>
                processThrowable=null;
                try
                {
                <!– do stuff –>
                }
                catch (Throwable blockThrowable)
                {
                processThrowable=blockThrowable;
                }
            </script>
        </scriptTask>

And there would need to be 2 sequence flows for each scriptTask:

        <sequenceFlow id="scriptTask1NextRealTarget" name="" sourceRef="scriptTask1" targetRef="nextRealTarget">
            <conditionExpression>${null==processThrowable}</conditionExpression>
        </sequenceFlow>
        <sequenceFlow id="scriptTask1HandleThrowable" name="" sourceRef="scriptTask1" targetRef="handleThrowable">
            <conditionExpression>${null!=processThrowable}</conditionExpression>
        </sequenceFlow>

We've tested this solution.

The issue is that the outflow of each scriptTask has a decision flow, which gets uglier as the process gets more complex.

We're open to better, more general solutions, if anyone has one.

Thanks!

Re: Timeout trying to lock table 'ACT_HI_ACTINST' [50200-132]

ronnie_and_sand — Mon, 05 Dec 2011 21:53:25 GMT

One way to avoid all the BPMN branching is to modify the groovy source code to wrap a Throwable as a ScriptException when the eval method fails, as was done below. The same approach could be used for every groovy script task, but what follows (in the groovy source code) only has to be done once.

In any case, when a ScriptException is thrown instead of Throwable, the table lock errors are avoided. However, we have not been able to track down evidence/history/state of a process where a ScriptException was thrown. There is no record in ACT_HI_PROCINST nor ACT_HI_ACTINST.

Does anyone know where information about ScriptException processes are stored or, more generally, how ScriptException processes are handled by Activiti?

Thank You!

—

GroovyScriptEngineImpl.eval wrap of Throwable:

//        } catch (Exception e) {
//            throw new ScriptException(e);
        } catch (Throwable e) {
            throw new ScriptException(new Exception(e));