How long does Alctiviti store runtime data?

[bwestrich]

Hello,

I'm looking at the excellent query api's provided by Activiti to see if they will meet my needs.

Some of these (for example, process instance query, accessed via engine.getRuntimeService.createProcessInstanceQuery) go against data stored in the runtime database tables (e.g. ACT_RU_*, such as ACT_RU_VARIABLE).

The user manual states the following about the runtime database tables:
ACT_RU_*: 'RE' (sic) stands for runtime. These are the runtime tables, that contain the runtime data of process instances, user tasks,variables, jobs, etc. Activiti only stores the runtime data during process instance execution, and removes the records when a process instance ends. This keeps the runtime tables small and fast.

I'm noticing however that these tables are not getting cleared out when process instances end. 

Anyone know why these tables are not getting cleared of data? 

If this is a "feature", I'll likely continue using these tables not only for runtime but also for historical queries. If this is a "bug", I'll look at using the history tables for historical queries instead….

Brian

[thilo_ginkel]

Some of these (for example, process instance query, accessed via engine.getRuntimeService.createProcessInstanceQuery) go against data stored in the runtime database tables (e.g. ACT_RU_*, such as ACT_RU_VARIABLE). […]

Anyone know why these tables are not getting cleared of data?

From my experience, Activiti is working as documented, i.e., the ACT_RU_* tables only hold information for as long as a process instance lives. After that, the data will only be available from the ACT_HI_* tables (given a sufficient history level).

Are you certain that the process instances in question have really ended?