Intermediate Timer Catch Event
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-28-2016 10:53 AM
Hi,
I am new to activiti, and trying to understand and implement a intermediate timer events.
I want to instantiate many processes(say 2000-3000) for intermediate catch event ( which have a timer definition to fire at specific date). So here the timer for each instance may be longer (eg 2-3 months) so could you please tell me does this implementation cause any overhead on the cpu and memory ? (I mean will these process instances (threads) be waiting or go into sleep state or they are only bought into execution again when timer fires at specific date and time like the timer start event)
Also I want to know if I can update the existing intermediate catch event with a different date at some other point before the timer ends??
Thirdly, could you also tell me if I can attach any identifier along with the instance of my intermediate timer event so that I can update that specific one later when needed?
Thank you
I am new to activiti, and trying to understand and implement a intermediate timer events.
I want to instantiate many processes(say 2000-3000) for intermediate catch event ( which have a timer definition to fire at specific date). So here the timer for each instance may be longer (eg 2-3 months) so could you please tell me does this implementation cause any overhead on the cpu and memory ? (I mean will these process instances (threads) be waiting or go into sleep state or they are only bought into execution again when timer fires at specific date and time like the timer start event)
Also I want to know if I can update the existing intermediate catch event with a different date at some other point before the timer ends??
Thirdly, could you also tell me if I can attach any identifier along with the instance of my intermediate timer event so that I can update that specific one later when needed?
Thank you
Labels:
- Labels:
-
Archive
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-29-2016 03:19 AM
> so could you please tell me does this implementation cause any overhead on the cpu and memory ?
No, none at all. Once a process instance reaches a wait state it is saved in the database. it can be there forever. No resources are consumed.
> Also I want to know if I can update the existing intermediate catch event with a different date at some other point before the timer ends
Yes, it will map to a Job. That job has a due date that you can change.
> could you also tell me if I can attach any identifier along with the instance of my intermediate timer event so that I can update that specific one later when needed
Yes, use a businessKey for your process instance or use a process variable.
No, none at all. Once a process instance reaches a wait state it is saved in the database. it can be there forever. No resources are consumed.
> Also I want to know if I can update the existing intermediate catch event with a different date at some other point before the timer ends
Yes, it will map to a Job. That job has a due date that you can change.
> could you also tell me if I can attach any identifier along with the instance of my intermediate timer event so that I can update that specific one later when needed
Yes, use a businessKey for your process instance or use a process variable.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-29-2016 03:46 AM
Thank you for ur reply.
In the update operation as you mentioned it will map to a job, I want to know if you have any Api to update the timer event, or should I write a query on the activitii database explicitly?
Also could u plz tell me if u have an Api to delete timer event?
Thank you
In the update operation as you mentioned it will map to a job, I want to know if you have any Api to update the timer event, or should I write a query on the activitii database explicitly?
Also could u plz tell me if u have an Api to delete timer event?
Thank you
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2016 05:47 PM
Thank you for ur reply.
In the update operation as you mentioned it will map to a job, I want to know if you have any Api to update the timer event, or should I write a query on the activitii database explicitly?
Also could u plz tell me if u have an Api to delete timer event?
Thank you
—
Archana
In the update operation as you mentioned it will map to a job, I want to know if you have any Api to update the timer event, or should I write a query on the activitii database explicitly?
Also could u plz tell me if u have an Api to delete timer event?
Thank you
—
Archana
