ENGINE-09004 Warnings during parsing

Camunda 7 Topics Discussion & Questions
1

Hi everybody!
I need some help. I create step by step instruction (Get started with Camunda | docs.camunda.org)
i use camunda modeler , my process is valid, but not deploy. …
12-Jan-2017 16:38:24.884 WARNING [localhost-startStop-1] org.camunda.commons.logging.BaseLogger.logWarn ENGINE-09004 Warnings during parsing:

  • schema_reference.4: Failed to read schema document ‘BPMNDI.xsd’, because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not xsd:schema. | invoice.v1.bpmn | line 8 | column 96
  • schema_reference.4: Failed to read schema document ‘Semantic.xsd’, because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not xsd:schema. | invoice.v1.bpmn | line 9 | column 46
  • Exclusive Gateway ‘reviewSuccessful_gw’ has outgoing sequence flow ‘reviewSuccessful’ without condition which is not the default flow. We assume it to be the default flow, but it is bad modeling practice, better set the default flow in your gateway. | invoice.v1.bpmn | line 0 | column 0
    12-Jan-2017 16:38:24.885 SEVERE [localhost-startStop-1] org.camunda.commons.logging.BaseLogger.logError ENGINE-16004 Exception while closing command context: ENGINE-09005 Could not parse BPMN process. Errors:
  • src-resolve: Cannot resolve the name ‘extension’ to a(n) ‘element declaration’ component. | invoice.v1.bpmn | line 15 | column 70
  • src-resolve: Cannot resolve the name ‘rootElement’ to a(n) ‘element declaration’ component. | invoice.v1.bpmn | line 16 | column 72
  • src-resolve: Cannot resolve the name ‘bpmndi:BPMNDiagram’ to a(n) ‘element declaration’ component. | invoice.v1.bpmn | line 17 | column 79
  • src-resolve: Cannot resolve the name ‘relationship’ to a(n) ‘element declaration’ component. | invoice.v1.bpmn | line 18 | column 73
  • cvc-complex-type.2.4.a: Invalid content was found starting with element ‘dataStore’. One of ‘{“http://www.omg.org/spec/BPMN/20100524/MODEL”:import}’ is expected. | invoice.v1.bpmn | line 3 | column 100
  • cvc-elt.4.2: Cannot resolve ‘tFormalExpression’ to a type definition for element ‘conditionExpression’. | invoice.v1.bpmn | line 52 | column 85
  • cvc-elt.4.2: Cannot resolve ‘tFormalExpression’ to a type definition for element ‘conditionExpression’. | invoice.v1.bpmn | line 57 | column 85
  • cvc-elt.4.2: Cannot resolve ‘tFormalExpression’ to a type definition for element ‘conditionExpression’. | invoice.v1.bpmn | line 88 | column 57
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 168 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 169 | column 65
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 170 | column 65
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 176 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 177 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 183 | column 65
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 184 | column 65
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 190 | column 65
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 191 | column 65
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 192 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 193 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 199 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 200 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 203 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 204 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 210 | column 65
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 211 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 217 | column 65
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 218 | column 65
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 219 | column 65
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 220 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 226 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 227 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 239 | column 65
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 240 | column 65
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 246 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 247 | column 67
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 253 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 254 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 255 | column 66
  • cvc-elt.4.2: Cannot resolve ‘omgdc:Point’ to a type definition for element ‘omgdi:waypoint’. | invoice.v1.bpmn | line 256 | column 66
    org.camunda.bpm.engine.ProcessEngineException: ENGINE-09005 Could not parse BPMN process. Errors:
2

Hi @marina31,

Could you please share your entire BPMN xml?

Cheers,
Roman

4

Load.bpmn (2.8 KB)

5

My problem is not in process , i take a simle example from here The Universal Process Orchestrator | Camunda (Simple Process
) and have the same problem(((
loan-approval.bpmn (3.7 KB)

6

catalina.2017-01-13.log (40.4 KB)
my full log file. PS: there is no any error whan i install app

7

Hi @marina31,

Deploying the loan-approval.bpmn or the other BPMN models from https://camunda.org/examples/ works without any warnings or errors.

But I am not able to deploy your attached Load.bpm model. There the camunda namespace missing inside bpmn:definitions elements. It must look like this:

<bpmn:definitions xmlns:bpmn="http://www.omg.org/spec/BPMN/20100524/MODEL"
                  xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI"
                  xmlns:di="http://www.omg.org/spec/DD/20100524/DI"
                  xmlns:dc="http://www.omg.org/spec/DD/20100524/DC"
                  xmlns:camunda="http://camunda.org/schema/1.0/bpmn"
                  id="Definitions_1"
                  targetNamespace="http://bpmn.io/schema/bpmn"
                  exporter="Camunda Modeler" exporterVersion="1.5.1">

Did you change the loan-approval.bpmn example in any way?

Cheers,
Roman

8

Dear Roman! Thank you very much for you answer. I take loan-approval.bpmn as is(from example i take total prodject without any change).Project compile ok(no error ,no warring), but whan i try to deploy…cant undestand whats wrong…

9

Marina,
Although i’m no expert on Camunda this sounds like a tomcat configuration issue.
Which version of camunda are you using and are you sure tomcat has all the required camunda libraries?
You can quickly test this by deploying your war to the camunda tomcat 7.6 distribution bundle.
Good luck!

10

Dear Davekant thank you very much for your advice! unfortunately, i have not any lucks with camunda(((. I use apache-tomcat-8.0.24( from this link Download Open Source Workflow Software | Camunda). Today i try it again(delete everything and dounload), but result is the same…In tomcat pannel i see that /camunda-invoice start-false…

printscreen.png1600×900 203 KB

11

Hi Marina,

in your catalina.log some errors show that XSD files cannot be read:

13-Jan-2017 13:56:56.403 WARNING [localhost-startStop-1] org.camunda.commons.logging.BaseLogger.logWarn ENGINE-09004 Warnings during parsing: 
* schema_reference.4: Failed to read schema document 'BPMNDI.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. | loan-approval.bpmn | line 8 | column 96
* schema_reference.4: Failed to read schema document 'Semantic.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. | loan-approval.bpmn | line 9 | column 46

Also from the log I see that the location of the apache server contains some special characters:

13-Jan-2017 13:56:47.890 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\Èñõîäíèêè\camunda\server\apache-tomcat-8.0.24
13-Jan-2017 13:56:54.187 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive C:\Èñõîäíèêè\camunda\server\apache-tomcat-8.0.24\webapps\loan-approval-0.1.0-SNAPSHOT.war

I’m not sure but it could be that either Java or Camunda is not able to handle a path starting with C:\Èñõîäíèêè\.

Could you test your setup in a path without special characters?

Cheers,
Sebastian

4 Likes
12

Dear Sebastian! You are my hero:)I spend 48 hour for this stupid error!
of course, way always must be in latin style!
Thank you very much!

13

“You are my hero:)” too lol

Replying only to reinforce this solution: If your Camunda installation returns crazy errors on creating processes, see you path and remove any special characters! I had the same issue, and a “í” was the problem!

My question is: should it be a bug or feature, to be corrected on new releases? Maybe an error during installation should be better than this issue during the process creation!