Hi all,
I was able to crack this process instance persistence issue, got past the above error by making modifications to the AuditLog.hbm.xml file (attached along), hiberante-cfg.xml and persistence.xml.
I had to ensure that these files are present in all the jars in the following location:
- jbpm-installer\runtime\jbpm-bam-5.1.0.M1.jar -- AuditLog.hbm.xml & hibernate.cfg.xml
- jbpm-installer\runtime\jbpm-human-task-5.1.0.M1.jar -- persistence.xml
- jbpm-installer\jboss-5.1.0.GA\server\default\deploy\jbpm-gwt-console-server.war\web-inf\classes\META-INF --- hibernate.cfg.xml & Persistence.xml
- Note : - jbpm-installer\jboss-5.1.0.GA\server\default\deploy\jbpm-gwt-console-server.war\web-inf\classes\hibernate.cfg.xml comes from ant install.demo, if at all you have a proper file in jbpm-installer\db folder it would ensure its presence here
- jbpm-installer\jboss-5.1.0.GA\server\default\deploy\jbpm-gwt-console-server.war\web-inf\lib\jbpm-bam-5.1.0.M1.jar -- AuditLog.hbm.xml & hibernate.cfg.xml
- jbpm-installer\jboss-5.1.0.GA\server\default\deploy\jbpm-gwt-console-server.war\web-inf\lib\jbpm-bam-5.1.0.M1.jar\META-INF -- persistence.xml
Now, iam able to see both process instance and as well the pending tasks even after a server and task service restart.
I also had to include the cloumn named "nodeName" in the nodeInstanceLog table as i had all my hiberante to validate the db, rather than create, but hope this hould bot be a concern.
Kris,
If we could ensure that demo build process(ant install.demo does it in a few places, but not all and there is no means to modify the AuditLog.hbm.xml without going inside the jars) includes this in all of the jars, it would be helpful for configuration.
Regards,
Aparna