JBPM database contains orphaned records in the SOA platform
Issue
- During process execution, we create variables and delete them again by calling context.getContextInstance().deleteVariable( variableName );
- We have installed a cron job to periodically delete ended process instances by calling GraphSession.deleteProcessInstance.
At the end all process instences get deleted, but the following tables still hold records:
- JBPM_VARIABLEINSTANCE
- JBPM_BYTEARRAY
- JBPM_BYTEBLOCK
Environment
-
JBoss SOA Platform (SOA-P) 4.3 CP01 / jBPM 3.2.5_SP5
-
JBoss SOA Platform (SOA-P) 4.3 CP02 / jBPM 3.2.7 / jBPM 3.2.8
-
JBoss SOA Platform (SOA-P) 5 / jBPM 3.2.7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
