| Summary: | Jbpm-console error was found due to "ProcessInstanceLog is not mapped " | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Ryan Zhang <rzhang> | ||||||
| Component: | BRM (Guvnor) | Assignee: | Toni Rikkola <trikkola> | ||||||
| Status: | VERIFIED --- | QA Contact: | Lukáš Petrovický <lpetrovi> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | BRMS 5.3.0.GA | CC: | jcoleman, kverlaen, trikkola | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | BRMS 5.3.0.GA | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | Type: | --- | |||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Ryan Zhang
2012-01-22 05:10:52 UTC
Created attachment 556747 [details]
server.log
Created attachment 556748 [details]
jbpm-console-snapshot.png
I am looking for a workaround to this issue in order to pass the ER3 to QE ASAP.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
The standalone server which can reproduce the issue can be downloaded at http://download.devel.redhat.com/brewroot/work/tasks/9604/3959604/org/jboss/brms-p/5.3.0.BRMS-ER3/brms-p-5.3.0.BRMS-ER3-standalone.zip
I moved the AuditLog.hbm.xml from jbpm-bam.jar/AuditLog.hbm.xml to jbpm-bam.jar/META-INF/AuditLog.hbm.xml, then the problem disappeared. I temporarily did this patch in platform build level. Please fix it in jbpm branch. Thanks We tried to make sure you can configure all persistence in one persistence.xml, so I think just adding these classes to the (already existing) persistence.xml should solve the issue: <class>org.jbpm.process.audit.ProcessInstanceLog</class> <class>org.jbpm.process.audit.NodeInstanceLog</class> <class>org.jbpm.process.audit.VariableInstanceLog</class> Yes, This issue is fixed as Bugzilla 784004 was resolved. Please verify the issue on 5.3 ER4. Where can I get the jbpm-sample-repository.xml? Please attach it or add a link. Zuzana, I understood why you can't find it since the actual name of the file is jbpm_example_repository.xml You can find it in relative path: [rzhang@jawa37g3 brms-standalone-5.3.0]$ find . -name "jbpm_example_repository.xml" ./jboss-as/server/production/deploy/jboss-brms.war/WEB-INF/classes/jbpm_example_repository.xml ./jboss-as/server/default/deploy/jboss-brms.war/WEB-INF/classes/jbpm_example_repository.xml Hi Ryan. I've removed the instructions you provided from the technical note field as notes in that field are used for the release notes. Thanks Lee Deleted Technical Notes Contents. Old Contents: The standalone server which can reproduce the issue can be downloaded at http://download.devel.redhat.com/brewroot/work/tasks/9604/3959604/org/jboss/brms-p/5.3.0.BRMS-ER3/brms-p-5.3.0.BRMS-ER3-standalone.zip |