timer problems 7.8.0

[lesch...@gmail.com]

Using 7.8.0 Final with the new designer. Created a fairly simple test process with a start node, an email task and an end node.

1st problem

The start node is of type start timer and the timer itself is configured as "Fire multiple times" with a cron expression of "5m".

So we expect to get an email every 5 minutes after the creation of a process instance. And it does exactly this, so far so good.

BUT:

After cancelling the process instance through the workbench, and making sure it's no longer active, we still keep receiving

this email every 5 minutes. It looks like a re-incarnation of https://issues.jboss.org/browse/JBPM-236 to me.

Can someone comment please on this? I wouldn't expect a process instance no longer being active still executing tasks.

2nd problem

When changing the start time in the above mentioned configuration to either "Fire multiple times" but with an ISO expression of

"R/PT5M", which to my understanding should do the exact same thing like the cron expression "5m", the timer does not fire. Never.

The same happens (or better does not happen), when using an ISO expression in the "Fire at a specific date" field like "2018-07-24T16:45:00+02:00"

It builds, deploys happily, the process instance gets created but then just sits there without ever firing at the specified time.

What am I doing wrong here?

TIA,

Paul

[Maciej Swiderski]

Paul,

On 24 Jul 2018, at 17:34, lesch...@gmail.com wrote:

Using 7.8.0 Final with the new designer. Created a fairly simple test process with a start node, an email task and an end node.

1st problem

The start node is of type start timer and the timer itself is configured as "Fire multiple times" with a cron expression of "5m".

So we expect to get an email every 5 minutes after the creation of a process instance. And it does exactly this, so far so good.

BUT:

After cancelling the process instance through the workbench, and making sure it's no longer active, we still keep receiving

this email every 5 minutes. It looks like a re-incarnation of https://issues.jboss.org/browse/JBPM-236 to me.

Can someone comment please on this? I wouldn't expect a process instance no longer being active still executing tasks.

first of all a bit of clarification on how start timer nodes work - they are not intended to be started manually - they will register timer (in your case) to fire every five minutes - but this means that every 5 minutes a new process instance is created.

if you want to stop firing every 5 minutes you will have to remove the deployment unit/kie container so it will unregister that timer.

So most likely what you need is intermediate timer catch event with timeCycle definition.

2nd problem

When changing the start time in the above mentioned configuration to either "Fire multiple times" but with an ISO expression of

"R/PT5M", which to my understanding should do the exact same thing like the cron expression "5m", the timer does not fire. Never.

The same happens (or better does not happen), when using an ISO expression in the "Fire at a specific date" field like "2018-07-24T16:45:00+02:00"

It builds, deploys happily, the process instance gets created but then just sits there without ever firing at the specified time.

this does not sound right, could you export your bpmn2 and share here?

Maciej

What am I doing wrong here?

TIA,

Paul

--
You received this message because you are subscribed to the Google Groups "jBPM Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+...@googlegroups.com.
To post to this group, send email to jbpm-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/c3888076-c3e7-4ee3-b693-7427a4f635f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[lesch...@gmail.com]

Thanks for the quick reply!

On Wednesday, July 25, 2018 at 9:51:33 AM UTC+2, Maciej Swiderski wrote:

1st problem

The start node is of type start timer and the timer itself is configured as "Fire multiple times" with a cron expression of "5m".

So we expect to get an email every 5 minutes after the creation of a process instance. And it does exactly this, so far so good.

BUT:

After cancelling the process instance through the workbench, and making sure it's no longer active, we still keep receiving

this email every 5 minutes. It looks like a re-incarnation of https://issues.jboss.org/browse/JBPM-236 to me.

Can someone comment please on this? I wouldn't expect a process instance no longer being active still executing tasks.

first of all a bit of clarification on how start timer nodes work - they are not intended to be started manually - they will register timer (in your case) to fire every five minutes - but this means that every 5 minutes a new process instance is created.

if you want to stop firing every 5 minutes you will have to remove the deployment unit/kie container so it will unregister that timer.

So most likely what you need is intermediate timer catch event with timeCycle definition.

Okay, got that. I read the documentation back and forth but haven't come across anything that describes this, sorry for missing that point!

I was just testing all available timer options and stumbled over this behaviour when setting a start node with a start time cycle, using an

intermediate catch event is fine. 

2nd problem

When changing the start time in the above mentioned configuration to either "Fire multiple times" but with an ISO expression of

"R/PT5M", which to my understanding should do the exact same thing like the cron expression "5m", the timer does not fire. Never.

The same happens (or better does not happen), when using an ISO expression in the "Fire at a specific date" field like "2018-07-24T16:45:00+02:00"

It builds, deploys happily, the process instance gets created but then just sits there without ever firing at the specified time.

this does not sound right, could you export your bpmn2 and share here?

After your hint, I retried this without manually starting an instance and now the start event does start correctly either after some time like "R/PT5M" or

at a given point in time like "2018-07-25T12:25:00+02:00"

Log timestamp shows it:

12:25:00,008 INFO  [stdout] (EJB default - 7) Executing work item WorkItem 10 [name=Log, state=0, processInstanceId=10, parameters{Message=TEST ISO, TaskName=Log}]

It seems only not to work after my previous attempts to mistakenly starting the instance manually.

So, again thanks for clearing that up!

Best, Paul