AnsweredAssumed Answered

Problem with Timer Intermediate Catching Event

Question asked by mindcrime on Apr 17, 2013
Latest reply on Apr 24, 2013 by mindcrime
Hi all, we're seeing some weird behavior using a Timer event.  We've reduced this to a very simple BPMN that does no more than this:

Begin with a None Start Event, transition to a Timer Intermediate Catching Event (specified with a duration, like, say, "PT2M" for 2 minutes), then flow out to a Task of some sort (more on that in a minute) and then flow to an End Event.

Running against a local PostgreSQL database, this works exactly as expected, with a Script Task, Service Task or User Task after the time.  But here's where it gets weird… if the backing database is our DEV instance of DB/2, this go wonky.  In that scenario, if you put a Service or Script task after the Timer, then execution never proceeds to that Task at all.  But if you put a User Task there, the User Task is created almost immediately after the process starts, and not after the 2 minute delay.

This is with Activiti 5.10, FWIW.

Has anybody seen anything like this before?  Any ideas what might be happening?

Outcomes