AnsweredAssumed Answered

Activiti workflow persistence after restarting server

Question asked by on Jun 11, 2013
Latest reply on Dec 5, 2013 by frederikheremans1
I have a question regarding why activiti is not persisting the already started workflow which is waiting on a user task after I restart my tomcat server?

I am using a workflow in which I have a user tasks which is assigned to a group. I am successfully able to connect to our ldap server which recognizes all the users and groups(Thanks to this forums). I am also able to start the bpmn workflow with message start event. One of the task in the flow is a user task with 4 mandatory form fields. After starting the flow, as user task is assigned to a group which I can see in Queued also. After assigning the task to myself,  if I restart the server, user task is no longer waiting and it completes the workflow. As fields are mandatory it throws an exception but still workflow is completed. SO I will not see a task in "My Task" after my server is started. I am using my own oracle db schema. 

Can someone help me with what am I missing? How can I make sure that the workflow which is waiting for user input always waits after restarting the tomcat server?

Thanks in advance,