JBPM database contains orphaned records in the SOA platform

Solution Unverified - Updated -

Issue

  1. During process execution, we create variables and delete them again by calling context.getContextInstance().deleteVariable( variableName );
  2. 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, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content