Red Hat Bugzilla – Bug 1004642
KPI initialization exceptions on server startup about jBPM tables not found
Last modified: 2014-08-06 16:10:19 EDT
Created attachment 793996 [details]
server.log with exceptions
Description of problem:
There is an "order of deployment" issue when dashbuilder.war and business-central.war are deployed together. Since some dashbuilder KPIs depend on existence of tables created by business-central it sometimes happens, that there is a lot of exceptions from dashbuilder complaining about nonexistent tables - see server.log attached.
: org.h2.jdbc.JdbcSQLException: Table "PROCESSINSTANCELOG" not found; SQL statement:
Version-Release number of selected component (if applicable):
BPMS 6.0.0 ER2 deployed on EAP 6.1.0, with default H2 in-memory database as datasource.
This problem happens only occasionaly, in about 10% of cases
Steps to Reproduce:
1. start eap with BPMS (dashbuilder + business central) deployed
2. wait for exceptions in EAP console.
Dashbuilder throws a lot of exceptions when initializing KPIs that depend on data from tables created by business-central.
In ideal case dashbuilder should be deployed AFTER business central deployment is finished. Would that be possible to guarantee order of deployment?
see server.log - search for 08:25:13,399
In server log we can clearly see that the required tables are created AFTER dashbuilder deployment is finished.
The jBPM Dashboard is dependent on the jBPM Engine so it's always mandatory to deploy first jBPM in any of its different flavours: jBPM Console, Kie-wb, ...
That prerequisite is highlighted here: https://github.com/droolsjbpm/jbpm-dashboard/blob/master/jbpm-dashboard-distributions/src/main/tomcat7/README.md#prerequisites
We should not expect any issues if we apply the right deployment order.
Are we still having issues despite of that?
can we somehow guarrantee the following order of deployment for the 2 applications that make up BPMS product?
From my point of view it seems, that deployment on EAP 6.1.0 runs in parralel which occasionaly leads to dashbuilder throwing above mentioned exceptions
Verified with BPMS 6.0.0 ER4