Completing/Deleting "Stuck" CMMN Instances

tjmac44 · March 30, 2021, 7:06pm

I have a CMMN that uses the event registry to listen to a few dozen events. Some of the earlier CMMN Deployments are still running and probably cant be completed because of incorrect event correlation.
Some of these are marked completable some are not.

What is the best way just to get rid of active cmmn instance, regardless of what the Planned Items state is?

I am almost at the point where I will write a SQL script to delete them, but dont know the downside of doing this way.

martin.grofcik · March 31, 2021, 12:45pm

Hi tjmac44,

SQL script: if you know what flowable does with cmmn and bpmn data you can do that. (do not forget async jobs, variables, history (update or delete…))

I would prefer to terminate cases or delete deployment (in that case history is also deleted), through rest endpoint or java api. I am just working on the tool which will be able to manage flowable items from the command line.

Regards
Martin

tjmac44 · March 31, 2021, 4:55pm

Deleting deployments is probably out as data needs to be preserved from case instances that completed successfully.

I do not see in the flowable api how to accomplish a terminate if the case instance still has active plan items.

martin.grofcik · March 31, 2021, 7:06pm

cmmnRuntimeService.terminateCaseInstance(String caseInstanceId);

tjmac44 · April 2, 2021, 4:16pm

Thanks again Martin.

The CLI project looks interesting. Can see uses when developing locally.

tjmac44 · April 2, 2021, 5:05pm

Found test case here:

github.com

flowable/flowable-engine/blob/main/modules/flowable-cmmn-engine/src/test/java/org/flowable/cmmn/test/runtime/CaseTaskTest.java

/* Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package org.flowable.cmmn.test.runtime;

import static org.assertj.core.api.Assertions.assertThat;
import static org.assertj.core.api.Assertions.assertThatThrownBy;
import static org.assertj.core.api.Assertions.tuple;

import java.util.Collections;
import java.util.List;

This file has been truncated. show original

martin.grofcik · April 2, 2021, 5:57pm

Topic		Replies	Views
Task completion and roll back Flowable Engine	1	700	November 4, 2019
CMMN Case Unit Test Best Practice Flowable Engine	2	458	June 1, 2020
CMMN: human task activated but not expected Flowable Engine	8	1075	April 10, 2019
Suspend a Case Instance Flowable Engine	1	336	October 28, 2020
CMMN Execution Listeners Flowable Engine	4	1066	February 16, 2018

Completing/Deleting "Stuck" CMMN Instances

Related Topics