topic Really simple timer start event throwing exception in Alfresco Archive

Really simple timer start event throwing exception

ct1 — Mon, 07 May 2012 21:19:42 GMT

Sirs:I am working with Activiti 5.9 on a Windows 7 OS.My use case is to have a process start at 8:00 a.m. each day. I wrote a very simple process with a Timer Start Event coded to start the process one time at the specified time (I am not trying to have the process start on a recurring basis yet, j

Re: Really simple timer start event throwing exception

trademak — Wed, 09 May 2012 10:14:00 GMT

Hi,

I just tested your example process in a simple unit test and that's working fine.
Also in the Activiti Explorer it's working fine.
Are you running multiple Activiti Engines on one database?

Best regards,

Re: Really simple timer start event throwing exception

ct1 — Fri, 11 May 2012 17:26:45 GMT

Thank you for testing this.

When I ran this test initially, only one Process Engine was running, the one used by Activiti Explorer.

I just reran the process in Explorer to confirm the behavior noted. It was the same as before.

Was your unit test written to catch the ActivitiOptimisticLockingException (and any other throwable)?

In your Expolorer test, did you see evidence in your log or console of a second deployment of all your processes when the Timer Start Event was supposed to start?

Thank you.

Re: Really simple timer start event throwing exception

trademak — Tue, 15 May 2012 15:08:04 GMT

Hi,

No my unit test didn't catch any exceptions.
In the Explorer I saw some log statements of processes retrieved multiple times, but that doesn't cause multiple deployments.
Do you see that processes are deployed multiple times in the Manage section?

Best regards,

Re: Really simple timer start event throwing exception

ct1 — Fri, 18 May 2012 14:50:40 GMT

Thank you for the information.

You were right, I did not notice the revision number of the process definitions getting higher, so it must be that the Deployer is simply parsing all the bpmn.20 files rather that deploying them. That is a relief; but then, with the possiblilty of hundreds of processes being defined in the database, the parsing may be repeated each time a Process Engine is created by the Java API calls. Would there be some way to direct the Deployer to parse only when the bpmn.20 file is loaded to run? Or to parse only the bpmn.20 files that have not been parsed?

There is still the question, should I expect an exception to be thrown when I use a timer start event to start a process? It seems reasonable to think that a process may be scheduled to start at a certain time and a used might be signed on to Explorer at that time completing a User Task in some other process.

Thank you for your continued help.