Description of problem:
Platform issue for https://issues.jboss.org/browse/JBPM-3543, to ensure this makes it into the platform, and to verify that no orphaned records remain in the database after the task has been ended.
With persistence enabled,when a process ends, it is removed from DBMS (ProcessInstanceInfo table)
However the tasks (Task table) and their data (Content table,PeopleAssignments* table,I18NText) related to the process are not deleted from DBMS causing an unnecessary growth of DBMS data.
We actually have an implementation in the community that cleans up tasks when the process instance related to it ends:
I don't think this is available in the product branch (5.2.x) however, but we can cherry-pick this.
This issue was agreed as a blocker, and has pm_ack. If we can commit to fixing this in the product branch, I will set the release flag for 5.3.1. Kris, can you comment?
This is already in 5.2.x
Complied information for Release Note purposes. Thanks for updates.
The data from Content table are not cleared after the process finishes. Other tables seem to be cleared properly.
I have added more verifications into the test case: https://github.com/droolsjbpm/jbpm/pull/144
Merged in 5.2.x and solved.
Mauricio Salatino <firstname.lastname@example.org> updated the status of jira JBPM-3543 to Closed
Mauricio Salatino <email@example.com> made a comment on jira JBPM-3543
- fixed in master and in 5.2.x
Verified on 5.3.1.BRMS CR1.
Employee 'firstname.lastname@example.org' has left the company.