topic Re: Process blocked in JOIN in Alfresco Archive

Process blocked in JOIN

jcosano — Tue, 21 Sep 2010 11:18:16 GMT

I have a process that split in 17 branches… and after join all before finish process.Now, the process is not finishing, and I suspect that is waiting in "join" state… DATE IN ACT_RU_EXECUTION is:ID_ REV_ PROC_INST_ID_ PARENT_ID_ PROC_DEF_ID_ SUPER_EXEC_ ACTIVITY_ID_ IS_ACTIVE_ IS_CON

Re: Process blocked in JOIN

jcosano — Tue, 21 Sep 2010 12:08:54 GMT

If I try to simulate process in a short time (playing with seconds or minutes) always works… but when is in real time (and units are days), process must be finish after seven days, and the process keep waiting in join state. (maybe some service is down but console is not showing errors)

Re: Process blocked in JOIN

jbarrez — Wed, 22 Sep 2010 05:58:52 GMT

Do you have the activiti logs? On the FINE level, it should perfect show what happens in a join, as it shows messages such as 'x out of y joined' etc..

Re: Process blocked in JOIN

jcosano — Wed, 22 Sep 2010 06:07:11 GMT

Activiti log is empty.

How can i activate activiti logs?

I didn't find this in activiti user guide…

Re: Process blocked in JOIN

jbarrez — Wed, 22 Sep 2010 06:30:37 GMT

Are you running in Tomcat or in a unit test?

Re: Process blocked in JOIN

frederikherema1 — Wed, 22 Sep 2010 06:34:02 GMT

If you are using aciviti 5.0.beta1 on tomcat using the demo-setup, the activiti.log is empty due to a bug (http://jira.codehaus.org/browse/ACT-94). Workaround is to edit the file in {tomcat.dir}/conf/logging.properties:

org.activiti.impl.util.LogUtil.LogUtil$LogFormatter should become
org.activiti.pvm.impl.util.LogUtil.LogUtil$LogFormatter

Re: Process blocked in JOIN

jcosano — Wed, 22 Sep 2010 07:00:05 GMT

I'm using tomcat 6.0.29 (installed by demo.setup).

I have a main class that deploy my process inside activiti, after with explorer I start instance (i have an error because there is not a form but process still running.. it is a group of serviceTask and timerEvents)

My logging.properties (tomcat/conf folder) not have any reference to
org.activiti.impl.util.LogUtil.LogUtil$LogFormatter
I added

handlers = java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level=FINEST
java.util.logging.ConsoleHandler.formatter=org.activiti.pvm.impl.util.LogUtil$LogFormatter

at the bottom of the file.. but activiti.log continues empty after running my process again.

Re: Process blocked in JOIN

frederikherema1 — Wed, 22 Sep 2010 07:13:18 GMT

Sorry, my bad.

The file is present in the activiti-engine-init webapplication, under /WEB-INF/classes/ which contains the error.
When changing the file, be sure to also alter it in 'setup/files/webapps/activiti-engine-init.war/WEB-INF/classes' so when you teardown/setup agian, it will be deployed in tomcat.

Re: Process blocked in JOIN

jcosano — Wed, 22 Sep 2010 07:30:52 GMT

I modify (two places), re-start tomcat, but activiti still empty.

activiti\apps\apache-tomcat-6.0.29\webapps\activiti-engine-init\WEB-INF\classes


handlers = org.apache.juli.FileHandler
.level = FINEST

org.apache.juli.FileHandler.level = FINEST
org.apache.juli.FileHandler.directory = ${catalina.base}/logs
org.apache.juli.FileHandler.prefix = activiti.
org.apache.juli.FileHandler.formatter=org.activiti.pvm.impl.util.LogUtil.LogUtil$LogFormatter

org.apache.level = SEVERE

Re: Process blocked in JOIN

frederikherema1 — Thu, 23 Sep 2010 08:41:17 GMT

Another option is to set the level for activiti-logging to fine in global tomcat log config (/conf/logging.properties), just add this line:

org.activiti.level=FINEST

Re: Process blocked in JOIN

jcosano — Thu, 23 Sep 2010 09:02:42 GMT

Ok, now we can see logs into tomcat output console.
Thank you!!!

Anyway activiti logfile is empty.

Re: Process blocked in JOIN

jcosano — Mon, 27 Sep 2010 07:55:16 GMT

Ok, now we have logs and for some reason last join (is not working fine):
At this point, I have 15 of 17 joined…

26-sep-2010 11:54:08 org.activiti.pvm.impl.runtime.AtomicOperationTransitionNotifyListenerTake execute
FINA: ConcurrentExecution[116] takes transition (oneTimerCOL)–>(javaServiceCOL)
26-sep-2010 11:54:08 org.activiti.pvm.impl.runtime.AtomicOperationActivityExecute execute
FINA: ConcurrentExecution[116] executes Activity(javaServiceCOL): org.activiti.engine.impl.bpmn.ServiceTaskDelegateActivityBehaviour
26-sep-2010 11:54:08 org.activiti.pvm.impl.runtime.AtomicOperationTransitionNotifyListenerTake execute
FINA: ConcurrentExecution[119] takes transition (oneTimerEMI)–>(javaServiceEMI)
26-sep-2010 11:54:08 org.activiti.pvm.impl.runtime.AtomicOperationActivityExecute execute
FINA: ConcurrentExecution[119] executes Activity(javaServiceEMI): org.activiti.engine.impl.bpmn.ServiceTaskDelegateActivityBehaviour
26-sep-2010 11:54:13 org.activiti.engine.impl.bpmn.BpmnActivityBehavior performOutgoingBehavior
FINA: Leaving activity 'javaServiceEMI'
26-sep-2010 11:54:13 org.activiti.pvm.impl.runtime.AtomicOperationTransitionNotifyListenerTake execute
FINA: ConcurrentExecution[119] takes transition (javaServiceEMI)–>(exclusiveEMI)
26-sep-2010 11:54:13 org.activiti.pvm.impl.runtime.AtomicOperationActivityExecute execute
FINA: ConcurrentExecution[119] executes Activity(exclusiveEMI): org.activiti.engine.impl.bpmn.ExclusiveGatewayActivity
26-sep-2010 11:54:13 org.activiti.engine.impl.bpmn.ExclusiveGatewayActivity leave
FINA: Leaving activity 'exclusiveEMI'
26-sep-2010 11:54:13 org.activiti.engine.impl.bpmn.ExclusiveGatewayActivity leave
FINA: Sequence flow 'flowEMI2 'selected as outgoing sequence flow.
26-sep-2010 11:54:13 org.activiti.pvm.impl.runtime.AtomicOperationTransitionNotifyListenerTake execute
FINA: ConcurrentExecution[119] takes transition (exclusiveEMI)–flowEMI2–>(join)
26-sep-2010 11:54:13 org.activiti.pvm.impl.runtime.AtomicOperationActivityExecute execute
FINA: ConcurrentExecution[119] executes Activity(join): org.activiti.engine.impl.bpmn.ParallelGatewayActivity
26-sep-2010 11:54:13 org.activiti.engine.impl.bpmn.ParallelGatewayActivity execute
FINA: parallel gateway 'join' does not activate: 16 of 17 joined
26-sep-2010 11:54:13 org.activiti.engine.impl.bpmn.BpmnActivityBehavior performOutgoingBehavior
FINA: Leaving activity 'javaServiceCOL'
26-sep-2010 11:54:13 org.activiti.pvm.impl.runtime.AtomicOperationTransitionNotifyListenerTake execute
FINA: ConcurrentExecution[116] takes transition (javaServiceCOL)–>(exclusiveCOL)
26-sep-2010 11:54:13 org.activiti.pvm.impl.runtime.AtomicOperationActivityExecute execute
FINA: ConcurrentExecution[116] executes Activity(exclusiveCOL): org.activiti.engine.impl.bpmn.ExclusiveGatewayActivity
26-sep-2010 11:54:13 org.activiti.engine.impl.bpmn.ExclusiveGatewayActivity leave
FINA: Leaving activity 'exclusiveCOL'
26-sep-2010 11:54:13 org.activiti.engine.impl.bpmn.ExclusiveGatewayActivity leave
FINA: Sequence flow 'flowCOL2 'selected as outgoing sequence flow.
26-sep-2010 11:54:13 org.activiti.pvm.impl.runtime.AtomicOperationTransitionNotifyListenerTake execute
FINA: ConcurrentExecution[116] takes transition (exclusiveCOL)–flowCOL2–>(join)
26-sep-2010 11:54:13 org.activiti.pvm.impl.runtime.AtomicOperationActivityExecute execute
FINA: ConcurrentExecution[116] executes Activity(join): org.activiti.engine.impl.bpmn.ParallelGatewayActivity
26-sep-2010 11:54:13 org.activiti.engine.impl.bpmn.ParallelGatewayActivity execute
FINA: parallel gateway 'join' does not activate: 16 of 17 joined

Re: Process blocked in JOIN

tombaeyens — Mon, 27 Sep 2010 14:45:24 GMT

can you try with 2 or 3 concurrent paths? if you can reproduce the problem with 2 or 3 paths, it's much easier to verify. as these logs don't seem to be complete.

if that works, then you can scale out to 17 concurrent paths.

only this release (to be released end of week) we added checks for optimistic locking. so if there is any concurrency in this test, then it's best to wait and test with 5.0.beta2

Re: Process blocked in JOIN

jcosano — Mon, 27 Sep 2010 15:10:21 GMT

I think that is better waiting for 5.0.beta2.

All small test (playing with seconds or minutes and 5 paths) works fine.
And with all paths, test are working fine too, but for some reason, when the process is playing 1 time at day, all weeks fails, looking logs we can see that last joined is done but counter fails.

I suppose that problem should be concurrency.