Deploy DNM to docker platform (7.13): ENGINE-22004 Unable to transform DMN resource 'dinnerDecisions.dmn'. [ deploy-error ]

Camunda 7 Topics Discussion & Questions
1

We get ENGINE-22004 Unable to transform DMN resource ‘dinnerDecisions.dmn’. [ deploy-error ] when deploying the tutorial (or anything else, also the running code from last year) to the camunda/camunda-bpm-platform:latest (tomcat) docker instances we run on Ubuntu Linux. The command /engine-rest/version returns {“version”:“7.13.0-SNAPSHOT”}.

Deploying locally works, according to the co-worker running MacOS X. Also some older modelers seem to work; this still has to be verified, though. The failed deployment shown here was done with modeler 4.11.1-win-x64. All community editions.

Could it be a problem with DMN versions and namespaces? 1.1 vs. 1.3? Or is that too far off?
Are there any known problems with reverse proxy setups? I doubt it’s there, though, since the API can definitely be reached and the file reached the server.

First lines of the log from the container are:

WARNING [http-nio-8080-exec-6] org.camunda.commons.logging.BaseLogger.logWarn ENGINE-REST-HTTP500 org.camunda.bpm.engine.ProcessEngineException: ENGINE-22004 Unable to transform DMN resource 'dinnerDecisions.dmn'.
        at org.camunda.bpm.engine.impl.dmn.DecisionLogger.exceptionParseDmnResource(DecisionLogger.java:59)
        at org.camunda.bpm.engine.impl.dmn.deployer.DecisionRequirementsDefinitionDeployer.transformDefinitions(DecisionRequirementsDefinitionDeployer.java:67)
        at org.camunda.bpm.engine.impl.AbstractDefinitionDeployer.transformResource(AbstractDefinitionDeployer.java:99)
        at org.camunda.bpm.engine.impl.AbstractDefinitionDeployer.parseDefinitionResources(AbstractDefinitionDeployer.java:74)
        at org.camunda.bpm.engine.impl.AbstractDefinitionDeployer.deploy(AbstractDefinitionDeployer.java:64)
        at org.camunda.bpm.engine.impl.persistence.deploy.cache.CacheDeployer$1.call(CacheDeployer.java:54)
        at org.camunda.bpm.engine.impl.persistence.deploy.cache.CacheDeployer$1.call(CacheDeployer.java:51)
        at org.camunda.bpm.engine.impl.interceptor.CommandContext.runWithoutAuthorization(CommandContext.java:537)
        at org.camunda.bpm.engine.impl.persistence.deploy.cache.CacheDeployer.deploy(CacheDeployer.java:51)
        at org.camunda.bpm.engine.impl.persistence.deploy.cache.DeploymentCache.deploy(DeploymentCache.java:67)
        at org.camunda.bpm.engine.impl.persistence.entity.DeploymentManager.insertDeployment(DeploymentManager.java:65)
        at org.camunda.bpm.engine.impl.cmd.DeployCmd.deploy(DeployCmd.java:255)
        at org.camunda.bpm.engine.impl.cmd.DeployCmd$1.call(DeployCmd.java:156)
        at org.camunda.bpm.engine.impl.cmd.DeployCmd$1.call(DeployCmd.java:142)
        at org.camunda.bpm.engine.impl.interceptor.CommandContext.runWithoutAuthorization(CommandContext.java:537)
        at org.camunda.bpm.engine.impl.cmd.DeployCmd.doExecute(DeployCmd.java:142)
        at org.camunda.bpm.engine.impl.cmd.DeployCmd.execute(DeployCmd.java:102)
        at org.camunda.bpm.engine.impl.cmd.DeployCmd.execute(DeployCmd.java:82)
        at org.camunda.bpm.engine.impl.interceptor.CommandExecutorImpl.execute(CommandExecutorImpl.java:28)
        at org.camunda.bpm.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:110)
        at org.camunda.bpm.engine.impl.interceptor.ProcessApplicationContextInterceptor.execute(ProcessApplicationContextInterceptor.java:70)
        at org.camunda.bpm.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:33)
        at org.camunda.bpm.engine.impl.RepositoryServiceImpl.deployWithResult(RepositoryServiceImpl.java:102)
        at org.camunda.bpm.engine.impl.repository.DeploymentBuilderImpl.deployWithResult(DeploymentBuilderImpl.java:270)
        at org.camunda.bpm.engine.rest.impl.DeploymentRestServiceImpl.createDeployment(DeploymentRestServiceImpl.java:98)

Any idea what to try next?

Regards
Peter

2

I set up Camunda run 7.16.0 without docker and deploying the same files works there.

3

It did not pull the new camunda:latest which is 7.16. There deployment works. So I consider this problem solved for the general public, but not for us since we are actually stuck with 7.13 at the moment due to dependencies. If you have an idea how 7.13 could work without needing an update I am still interested.

4