AnsweredAssumed Answered

Create Diagram On Deploy

Question asked by jatz on Apr 24, 2013
Latest reply on Apr 26, 2013 by jatz

I thought I will share on this forum an issue which we faced and maybe a suggestion on this.

We have a war running activiti as a jar withn it (Spring). When deploying to tomcat and starting up it worked fine.

The issue occurred when we used an automated tool which had fewer rights on this box. When deploying the server looked to hang after the first Activiti update statement was run.

We looked at everything but we could not understand the problem. When we looked at the thread dump the below showed up:

"main" prio=10 tid=0x000000000639e000 nid=0x5725 runnable [0x000000004060c000]
   java.lang.Thread.State: RUNNABLE
   at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
   at sun.awt.X11GraphicsEnvironment.access$200(
   at sun.awt.X11GraphicsEnvironment$
   at Method)
   at sun.awt.X11GraphicsEnvironment.<clinit>(
   at java.lang.Class.forName0(Native Method)
   at java.lang.Class.forName(
   at java.awt.GraphicsEnvironment.createGE(
   at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(
   - locked <0x00000000fbaae550> (a java.lang.Class for java.awt.GraphicsEnvironment)
   at java.awt.image.BufferedImage.createGraphics(
   at org.activiti.engine.impl.bpmn.diagram.ProcessDiagramCanvas.<init>(
   at org.activiti.engine.impl.bpmn.diagram.ProcessDiagramCanvas.<init>(
   at org.activiti.engine.impl.bpmn.diagram.ProcessDiagramGenerator.initProcessDiagramCanvas(
   at org.activiti.engine.impl.bpmn.diagram.ProcessDiagramGenerator.generateDiagram(
   at org.activiti.engine.impl.bpmn.diagram.ProcessDiagramGenerator.generateDiagram(
   at org.activiti.engine.impl.bpmn.diagram.ProcessDiagramGenerator.generatePngDiagram(
   at org.activiti.engine.impl.bpmn.deployer.BpmnDeployer.deploy(
   at org.activiti.engine.impl.persistence.deploy.DeploymentCache.deploy(
   at org.activiti.engine.impl.persistence.entity.DeploymentManager.insertDeployment(

This led us to change the processEngineConfiguration setting to config.setCreateDiagramOnDeploy(false) which resolved this issue.

The suggestion is that would it be better if we keep this setting to false as a default. Especially with automated deployments this could come up as an issue. Wanted to know your thoughts on this?