More than 4000 characters in DMN table input

Martin_Nagl · August 16, 2022, 4:14pm

Hi Camunda fans,

I’m having a problem when executing a DMN decision on an input string longer than 4000 characters. I am determining type of document based on document content. The decision itself executes OK, but right after that an exception occurs when camunda tries to insert an HistoricDecisionInputInstanceEntity into table ACT_HI_DEC_IN :

org.camunda.bpm.engine.ProcessEngineException: ENGINE-03004 Exception while executing Database Operation ‘INSERT HistoricDecisionInputInstanceEntity[17f601d4-1d79-11ed-819d-8c8d28c7c361]’ with message ’

Error flushing statements. Cause: org.apache.ibatis.executor.BatchExecutorException: org.camunda.bpm.engine.impl.history.event.HistoricDecisionInputInstanceEntity.insertHistoricDecisionInputInstance (batch index #3) failed. 2 prior sub executor(s) completed successfully, but will be rolled back. Cause: org.h2.jdbc.JdbcBatchUpdateException: Value too long for column “TEXT_ VARCHAR(4000)”: “STRINGDECODE('Lorem ipsum dolor sit amet, consectetur adipiscing elit. Etiam et odio nec velit bibendum blandit sit amet sed dui… (5008)”; SQL statement:

insert into ACT_HI_DEC_IN(
ID_,
DEC_INST_ID_,
CLAUSE_ID_,
CLAUSE_NAME_,
VAR_TYPE_,
BYTEARRAY_ID_,
DOUBLE_,
LONG_,
TEXT_,
TEXT2_,
TENANT_ID_,
CREATE_TIME_,
ROOT_PROC_INST_ID_,
REMOVAL_TIME_
) values (
?,
?,
?,
?,
?,
?,
?,
?,
?,
?,
?,
?,
?,
?
) [22001-200]

My decision table looks like this (simplified):

I have a unit test that can simulate the issue:

gist.github.com

https://gist.github.com/naglm/85e82fb826f6d735c23a43d9bf435876

ProcessTest.java

package com.example.workflow;

import static org.camunda.bpm.engine.test.assertions.bpmn.AbstractAssertions.init;
import static org.camunda.bpm.engine.test.assertions.bpmn.BpmnAwareTests.assertThat;

import java.util.Map;

import org.assertj.core.api.Assertions;
import org.camunda.bpm.engine.ProcessEngine;
import org.camunda.bpm.engine.variable.Variables;

This file has been truncated. show original

decision.dnm

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="https://www.omg.org/spec/DMN/20191111/MODEL/" xmlns:dmndi="https://www.omg.org/spec/DMN/20191111/DMNDI/" xmlns:dc="http://www.omg.org/spec/DMN/20180521/DC/" xmlns:biodi="http://bpmn.io/schema/dmn/biodi/2.0" id="Definitions_03vjjmw" name="DRD" namespace="http://camunda.org/schema/1.0/dmn" exporter="Camunda Modeler" exporterVersion="4.5.0">
  <decision id="ChooseDocumentType" name="Choose Document Type">
    <decisionTable id="DecisionTable_0dfobum" hitPolicy="FIRST">
      <input id="Input_1" label="documentContent" biodi:width="240">
        <inputExpression id="InputExpression_1" typeRef="string">
          <text>documentContent</text>
        </inputExpression>
      </input>
      <output id="Output_1" label="documentType" name="documentType" typeRef="string" />

This file has been truncated. show original

I am passing the documentContent parameter wrapped in Variables.objectValue(...) so that it is stored as object reference when passing to DMN engine. This seems to work OK for the decision engine itself, as I can see that it executes with a correct result. However I suspect that when Camunda creates HistoricDecisionInputInstanceEntity it always stores the value into text_ field and somehow does not store it as object reference. (my wild guess is DefaultDmnHistoryEventProducer.createHistoricDecisionInputInstances() where it takes the untyped value?).

How should I pass the parameter with more than 4000 characters into DMN table so that it does not cause exception when inserting into ACT_HI_DEC_IN table?

Thanks for your support

system · January 31, 2024, 10:24am