Hi Adam, by default the runtime data is not saved persistently so after restart the stored info is gone. You would need to configure other persistence than the default H2..see docs chapter 7 for more info: http://docs.jboss.org/jbpm/v5.1/userguide/ch07.html.
Hope this helps.
First of all thank You for answer.
If you look at 6 and 7 I say that after restart I can see the processes in the database... I managed to setup jbpm to use JPA and MySQL. So As I said after I restart jboss I can still see process instances in mysql database but server can't see it when it loads session... Are there other stepps other than changing JPA config to use mysql and make server load processes after restart?
since process history/instances log is maintained by jbpm-bam component and that comonent has its own persistance configuration (pure hibernate) there is a hibernate.cfg.xml file that defines how it should work/connect to db etc. Maybe there is some kind of issue, using different db, or whatever...
i changed the hibernate.conf.xml in the jbpm-bam and now i see the process instances after restart of the server. But i don't see any humantasks which not been edited. Which file i have to edit?
Human Task has its own persistence.xml that is bundled with jbpm-human-task jar file
I've changed this persistence. But I see the human tasks not yet.