]
Tom Baeyens updated JBPM-2360:
------------------------------
Fix Version/s: jBPM 4.1
(was: jBPM 4.0)
fix deletion of deployments in cluster
--------------------------------------
Key: JBPM-2360
URL:
https://jira.jboss.org/jira/browse/JBPM-2360
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Tom Baeyens
Fix For: jBPM 4.1
when a deployment gets deleted, the request arrives in one node of the cluster. that
node can remove the deployment and its process definition from the repository cache
immediately.
but how will the other nodes in the cluster know ?
some check with db access has to be added every time an object (process definition) is
fetched from the repository cache. alternatively this can also be enforced at those
locations where suspended must be checked: in the commands for starting a new execution,
signalling and so on.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: