Deployment Failed: Error Parsing XML

[philcio]

Hello Activiti community,

I am developing a BPMN process in Activiti. Whenever I add a signal definition to my process or leave the "collaboration" tag inside the XML file, I am getting a "Error Parsing XML" message.

Here is what I mean:

<blockcode>
<definitions xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:activiti="http://activiti.org/bpmn" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlnsmgdc="http://www.omg.org/spec/DD/20100524/DC" xmlnsmgdi="http://www.omg.org/spec/DD/20100524/DI" typeLanguage="http://www.w3.org/2001/XMLSchema" expressionLanguage="http://www.w3.org/1999/XPath" targetNamespace="http://www.activiti.org/test">

  <signal id="correctionDone" name="correctionDone"></signal>

  <collaboration id="Collaboration">
    <participant id="klausurstellung" name="Klausurstellung" processRef="klausurstellung"></participant>
  </collaboration>
 
<!– process –>
<!– the signal is  further defined within the process –>
</blockcode>

If I delete both, the collaboration tag and the signal definition inside of my BPMN diagram. The process deployment works.

This is the error stack trace:

<blockcode>
com.vaadin.event.ListenerMethod$MethodException: Invocation of method uploadFinished in org.activiti.explorer.ui.custom.UploadComponent failed.
   at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:530)
   at com.vaadin.event.EventRouter.fireEvent(EventRouter.java:164)
   at com.vaadin.ui.AbstractComponent.fireEvent(AbstractComponent.java:1219)
   at com.vaadin.ui.Upload.fireUploadInterrupted(Upload.java:731)
   at com.vaadin.ui.Upload$1.streamingFailed(Upload.java:1037)
   at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.streamToReceiver(AbstractCommunicationManager.java:619)
   at com.vaadin.terminal.gwt.server.AbstractCommunicationManager.doHandleSimpleMultipartFileUpload(AbstractCommunicationManager.java:476)
   at com.vaadin.terminal.gwt.server.CommunicationManager.handleFileUpload(CommunicationManager.java:259)
   at com.vaadin.terminal.gwt.server.AbstractApplicationServlet.service(AbstractApplicationServlet.java:495)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
   at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
   at org.activiti.explorer.filter.ExplorerFilter.doFilter(ExplorerFilter.java:44)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
   at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
   at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
   at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
   at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
   at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
   at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
   at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
   at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
   at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
   at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
   at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:315)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.NullPointerException
   at org.activiti.explorer.ui.management.deployment.DeploymentUploadReceiver.showUploadedDeployment(DeploymentUploadReceiver.java:114)
   at org.activiti.explorer.ui.management.deployment.DeploymentUploadReceiver.uploadFinished(DeploymentUploadReceiver.java:73)
   at org.activiti.explorer.ui.custom.UploadComponent.uploadFinished(UploadComponent.java:197)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:606)
   at com.vaadin.event.ListenerMethod.receiveEvent(ListenerMethod.java:510)
   … 31 more
</blockcode>

I have checked the forum and added the cxf dependencies to my Tomcat/lib folder.

Thanks in advance,
Philip

[jbarrez]

Collaborations are not supported in Activiti.

[philcio]

Thank you for your quick reply.

Actually, I am not intending to use collaborations. As soon as I add one pool (with 3 lanes) into my Activiti Designer diagram, it automatically generates the collaboration tag. Although I have only one pool in my diagram. Shouldn't I add the pool graphic to my diagram in order to make it work?

[jbarrez]

Could you post the full XML here so we can have a look?

[philcio]

Thank you for your reply and sorry for my late response. I fixed it by starting the process from scratch without adding a pool with lanes to the diagram. Now it works as intended.

[espe]

Hello,

I'm facing exactly the same issue, though I'm not using any collaboration or signals in the XML. Increasing log level didn't help either.
The only thing I can notice about my process is that is very big.
I am attaching you the process definition itself (it's the exact .bpmn file - I simply changed the extension to .txt).

Could it be the size of the definition an issue here?
What can I do to troubleshoot this?

[martin_grofcik]

Hi,

the cause is in the log

Caused by: org.activiti.engine.impl.juel.TreeBuilderException: Error parsing '#{calculate.div(R_lv_load_m, R_lv_load_m_sum)}': syntax error at position 12, encountered 'div', expected <IDENTIFIER>

Regards
Martin

[espe]

Hi,

Thanks for your reply. You are right "div" seems to be a reserved word for EL expressions http://docs.oracle.com/javaee/6/tutorial/doc/bnail.html

However, my real problem here is that I can't view the logs as you do. I am uploading the file through activiti-explorer and I don't see the log entry that you see in any of .log, .out, .err files of the server. I am running Weblogic. Am I supposed to configure something?

[martin_grofcik]

Hi,

I do not use activiti-explorer, but I would say that there is log4j configuration file somewhere.
http://activiti.org/userguide/index.html#loggingConfiguration

Regards
Martin

[espe]

Yes, I checked log4j configuration, everything seems to be ok. Anyway, I feel this is a different issue. I will open a different thread. How are you deploying and you see such logs? I will do the same.

In the meantime is it possible to check why this definition (attached) throws again the same error? Obviously I fixed the previous one. Sorry for asking, but I'm really clueless on this until I fix logging. Thanks for your valuable support.