cancel
Showing results for 
Search instead for 
Did you mean: 

Process not displaying in Activiti Explorer

zlatan316
Champ on-the-rise
Champ on-the-rise
Hello,

I am coming across an error where the diagram will deploy and Start successfully but it will not display in the pane when selected in 'My Instances'. The error given is as follows:

[usertask1]
Oct 21, 2014 11:01:11 AM org.restlet.engine.log.LogFilter afterHandle
INFO: 2014-10-21   11:01:11   10.117.91.135   -   159.167.125.228   8080   GET   /activiti-explorer/service/process-instance/88633/highlights   callback=jQuery17105653023972745423_1413885737757&_=1413885738910   200   231   0   10   http://159.167.125.228:8080   Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0; managedpc)   http://159.167.125.228:8080/activiti-explorer/diagram-viewer/index.html?processDefinitionId=liveProc...
Oct 21, 2014 11:01:14 AM org.restlet.resource.UniformResource doCatch
WARNING: Exception or error caught in resource
java.lang.NullPointerException
   at org.activiti.rest.diagram.services.ProcessDefinitionDiagramLayoutResource.getActivity(ProcessDefinitionDiagramLayoutResource.java:440)
   at org.activiti.rest.diagram.services.ProcessDefinitionDiagramLayoutResource.getDiagram(ProcessDefinitionDiagramLayoutResource.java:203)
   at sun.reflect.GeneratedMethodAccessor287.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:622)
   at org.restlet.resource.ServerResource.doHandle(ServerResource.java:452)
   at org.restlet.resource.ServerResource.get(ServerResource.java:648)
   at org.restlet.resource.ServerResource.doHandle(ServerResource.java:530)
   at org.restlet.resource.ServerResource.doNegotiatedHandle(ServerResource.java:590)
   at org.restlet.resource.ServerResource.doConditionalHandle(ServerResource.java:302)
   at org.restlet.resource.ServerResource.handle(ServerResource.java:849)
   at org.restlet.resource.Finder.handle(Finder.java:513)
   at org.restlet.routing.Filter.doHandle(Filter.java:159)
   at org.restlet.routing.Filter.handle(Filter.java:206)
   at org.restlet.routing.Router.doHandle(Router.java:500)
   at org.restlet.routing.Router.handle(Router.java:740)
   at org.restlet.routing.Filter.doHandle(Filter.java:159)
   at org.restlet.routing.Filter.handle(Filter.java:206)
   at org.restlet.routing.Filter.doHandle(Filter.java:159)
   at org.restlet.routing.Filter.handle(Filter.java:206)
   at org.restlet.routing.Filter.doHandle(Filter.java:159)
   at org.restlet.routing.Filter.handle(Filter.java:206)
   at org.restlet.routing.Filter.doHandle(Filter.java:159)
   at org.restlet.engine.application.StatusFilter.doHandle(StatusFilter.java:155)
   at org.restlet.routing.Filter.handle(Filter.java:206)
   at org.restlet.routing.Filter.doHandle(Filter.java:159)
   at org.restlet.routing.Filter.handle(Filter.java:206)
   at org.restlet.engine.ChainHelper.handle(ChainHelper.java:114)
   at org.restlet.engine.application.ApplicationHelper.handle(ApplicationHelper.java:75)
   at org.restlet.Application.handle(Application.java:391)
   at org.restlet.routing.Filter.doHandle(Filter.java:159)
   at org.restlet.routing.Filter.handle(Filter.java:206)
   at org.restlet.routing.Router.doHandle(Router.java:500)
   at org.restlet.routing.Router.handle(Router.java:740)
   at org.restlet.routing.Filter.doHandle(Filter.java:159)
   at org.restlet.routing.Filter.handle(Filter.java:206)
   at org.restlet.routing.Router.doHandle(Router.java:500)
   at org.restlet.routing.Router.handle(Router.java:740)
   at org.restlet.routing.Filter.doHandle(Filter.java:159)
   at org.restlet.routing.Filter.handle(Filter.java:206)
   at org.restlet.engine.ChainHelper.handle(ChainHelper.java:114)
   at org.restlet.Component.handle(Component.java:391)
   at org.restlet.Server.handle(Server.java:491)
   at org.restlet.engine.ServerHelper.handle(ServerHelper.java:74)
   at org.restlet.engine.http.HttpServerHelper.handle(HttpServerHelper.java:153)
   at org.restlet.ext.servlet.ServerServlet.service(ServerServlet.java:1031)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at org.activiti.explorer.filter.ExplorerFilter.doFilter(ExplorerFilter.java:44)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
   at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
   at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
   at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
   at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
   at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
   at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:857)
   at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
   at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
   at java.lang.Thread.run(Thread.java:701)


Can anyone give any pointers on why this is occuring?

With Regards,
Ibz
3 REPLIES 3

jbarrez
Star Contributor
Star Contributor
Which version of Activiti is this? I don't see anything in the current code that would cause that exception

zlatan316
Champ on-the-rise
Champ on-the-rise
This was with version 5.14. I have now fixed this issue.

I had an incorrectly named 'Called Element' item which when corrected, allowed the diagram to display in the My Instance window pane. However, I cannot understand why there wasn't an error related to the diagram not being able to find the Call Activity's 'called element' instead? Normally if you specify a incorrect process id in the 'called element' field, it complains about now being able to find the process id.

jbarrez
Star Contributor
Star Contributor
Yeah, that sounds very strange .. it should have shown the diagram anyway