Over a million developers have joined DZone.

Activiti TimerEvent Only Firing Once

· Java Zone

Microservices! They are everywhere, or at least, the term is. When should you use a microservice architecture? What factors should be considered when making that decision? Do the benefits outweigh the costs? Why is everyone so excited about them, anyway?  Brought to you in partnership with IBM.

This is just a mental note since I wasted hours on it a few months ago.  Then a colleague just did the same.

If you are developing a business process in Activiti, and your TimerEvent is only firing once, add the following parameter to your Activiti config:

<property name="jobExectuorActivate" value="true"/>

This is mentioned in the documentation, but only as a very small note:
http://www.activiti.org/userguide/index.html#timerEventDefinitions

"Note: timers are only fired when the job executor is enabled (i.e. jobExecutorActivate needs to be set to true in the activiti.cfg.xml, since the job executor is disabled by default)"

Hopefully this saves people some time.

 

Discover how the Watson team is further developing SDKs in Java, Node.js, Python, iOS, and Android to access these services and make programming easy. Brought to you in partnership with IBM.

Topics:

Published at DZone with permission of Brian O' Neill, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}