Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-3349

jBPM attempts redeploy of an invalid process-definition.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • jBPM 3.2.12
    • jBPM 3.2.11
    • Runtime Engine
    • None

      When a deployment of process definition fails then the jBPM engine tries to redeploy the process definition (currently 9 times). The retry attempt obviously cannot succeed because of errors still present in the definition. You will see something like this in the server log:

      08:59:06,788 ERROR [STDERR] org.jbpm.jpdl.JpdlException: failed to parse process document
      08:59:06,790 ERROR [STDERR] 	at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:148)
      08:59:06,790 ERROR [STDERR] 	at org.jbpm.graph.def.ProcessDefinition.parseXmlInputStream(ProcessDefinition.java:255)
      08:59:06,790 ERROR [STDERR] 	at org.jboss.soa.esb.qa.framework.DeployProcessAction.process(DeployProcessAction.java:62)
      08:59:06,790 ERROR [STDERR] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      08:59:06,790 ERROR [STDERR] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      08:59:06,790 ERROR [STDERR] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      08:59:06,790 ERROR [STDERR] 	at java.lang.reflect.Method.invoke(Method.java:597)
      08:59:06,790 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
      08:59:06,790 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.message.BeanConfigActionProcessor.process(BeanConfigActionProcessor.java:79)
      08:59:06,790 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:649)
      08:59:06,790 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:603)
      08:59:06,790 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:433)
      08:59:06,790 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:550)
      08:59:06,790 ERROR [STDERR] 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      08:59:06,790 ERROR [STDERR] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      08:59:06,790 ERROR [STDERR] 	at java.lang.Thread.run(Thread.java:619)
      08:59:06,791 ERROR [STDERR] Caused by: org.dom4j.DocumentException: Error on line 43 of document  : The element type "node" must be terminated by the matching end-tag "</node>". Nested exception: The element type "node" must be terminated by the matching end-tag "</node>".
      08:59:06,791 ERROR [STDERR] 	at org.dom4j.io.SAXReader.read(SAXReader.java:482)
      08:59:06,791 ERROR [STDERR] 	at org.jbpm.jpdl.xml.JpdlParser.parse(JpdlParser.java:76)
      08:59:06,791 ERROR [STDERR] 	at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:145)
      08:59:06,791 ERROR [STDERR] 	... 15 more
      08:59:06,791 INFO  [STDOUT] Deployment failed, retry attempt 0
      08:59:07,309 ERROR [STDERR] org.jbpm.jpdl.JpdlException: failed to parse process document
      08:59:07,310 ERROR [STDERR] 	at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:148)
      08:59:07,310 ERROR [STDERR] 	at org.jbpm.graph.def.ProcessDefinition.parseXmlInputStream(ProcessDefinition.java:255)
      08:59:07,310 ERROR [STDERR] 	at org.jboss.soa.esb.qa.framework.DeployProcessAction.process(DeployProcessAction.java:62)
      08:59:07,310 ERROR [STDERR] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      08:59:07,310 ERROR [STDERR] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      08:59:07,310 ERROR [STDERR] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      08:59:07,310 ERROR [STDERR] 	at java.lang.reflect.Method.invoke(Method.java:597)
      08:59:07,310 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
      08:59:07,310 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.message.BeanConfigActionProcessor.process(BeanConfigActionProcessor.java:79)
      08:59:07,310 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:649)
      08:59:07,310 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:603)
      08:59:07,310 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:433)
      08:59:07,310 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:550)
      08:59:07,310 ERROR [STDERR] 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      08:59:07,310 ERROR [STDERR] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      08:59:07,310 ERROR [STDERR] 	at java.lang.Thread.run(Thread.java:619)
      08:59:07,310 ERROR [STDERR] Caused by: org.dom4j.DocumentException: Error on line 43 of document  : The element type "node" must be terminated by the matching end-tag "</node>". Nested exception: The element type "node" must be terminated by the matching end-tag "</node>".
      08:59:07,310 ERROR [STDERR] 	at org.dom4j.io.SAXReader.read(SAXReader.java:482)
      08:59:07,310 ERROR [STDERR] 	at org.jbpm.jpdl.xml.JpdlParser.parse(JpdlParser.java:76)
      08:59:07,311 ERROR [STDERR] 	at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:145)
      08:59:07,311 ERROR [STDERR] 	... 15 more
      08:59:07,311 INFO  [STDOUT] Deployment failed, retry attempt 1
      ...
      

            marco.rietveld Marco Rietveld (Inactive)
            mbaluch@redhat.com Marek Baluch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: