Exception when starting Camunda

Workflows
,
1

Question on behalf of @thomas-soft-grove

I have the following exception when starting Camunda (which in turn starts a DS platform server)

c.m.a.d.s.BusinessModelInitializer       : Importing business models: classpath:/models/business/common/
c.m.a.d.m.b.BulkImportProblemReporter    : Error while importing models

com.mgmtp.a12.dataservices.exception.serialization.DocumentModelDeSerializationException: com.fasterxml.jackson.databind.JsonMappingException: Missing locale for localized text (through reference chain: com.mgmtp.a12.kernel.md.model.a12internal.DocumentModel["content"]->com.mgmtp.a12.kernel.md.model.a12internal.DocumentModelContent["modelRoot"]->com.mgmtp.a12.kernel.md.model.a12internal.DocumentModelRoot["rootGroups"]->java.util.ArrayList[0]->com.mgmtp.a12.kernel.md.model.a12internal.Group["elements"]->java.util.ArrayList[0]->com.mgmtp.a12.kernel.md.model.a12internal.Group["elements"]->java.util.ArrayList[0]->com.mgmtp.a12.kernel.md.model.a12internal.Field["label"])
        at com.mgmtp.a12.dataservices.utils.internal.DocumentModelUtils.deserializeDocumentModel(DocumentModelUtils.java:170)
.....        
Caused by: java.lang.IllegalArgumentException: Missing locale for localized text
        at com.mgmtp.a12.kernel.md.model.internal.service.serialization.LocalizedTextMapDeserializer.getLocaleFromLocalizedText(LocalizedTextMapDeserializer.java:48)
        at com.mgmtp.a12.kernel.md.model.internal.service.serialization.LocalizedTextMapDeserializer.deserialize(LocalizedTextMapDeserializer.java:38)
        at com.mgmtp.a12.kernel.md.model.internal.service.serialization.LocalizedTextMapDeserializer.deserialize(LocalizedTextMapDeserializer.java:20)
        at com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:129)
        at com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:313)
        ... 109 common frames omitted ```

How can I find out which model is invalid

The error message gives no clue, which of our 60 models is the culprit
2

Hi @ahmad-warm-vale ,

Please create a ticket for this. This is a DS model import which does not log the name of the model which caused the error. We can add logs. This is not workflows issue

3

Hi @tbajus,
Thank you for the information, I will create a ticket for that.

4

Any chance I can find out which model is incorrect with the current DS version (34.1.2)?

5

please put breakpoint here : <INTERNAL_LINK>

And then backtract the call to DocumentModelResourceExpander#addModel there you will find the path to the model that has caused the issue.

I am sorry that this is not more convenient