Bug 1004358

Summary: Dashboard throws errors on deployment: "Error in load() SQLDataset." and "Error serializing data provider: null"
Product: [Retired] JBoss BPMS Platform 6 Reporter: Jiri Svitak <jsvitak>
Component: BAMAssignee: David Gutierrez <dgutierr>
Status: CLOSED WONTFIX QA Contact: Jiri Svitak <jsvitak>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: mbaluch
Target Milestone: ER4   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-18 13:59:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
server.log
none
mysql-ds.xml none

Description Jiri Svitak 2013-09-04 13:19:45 UTC
Created attachment 793666 [details]
server.log

BPMS ER2 deployment throws these errors:

15:06:11,621 ERROR [org.jboss.dashboard.dataset.sql.SQLDataSet] (ServerService Thread Pool -- 55) Error in load() SQLDataset. SQL = select total.processname, coalesce(total.instances,0) total, coalesce(active.instances_act,0) active, coalesce(completed.instances_compl,0) completed, coalesce(pending.instances_pend,0) pending, coalesce(suspended.instances_susp,0) suspended, coalesce(aborted.instances_abrt,0) aborted

...

15:06:11,629 ERROR [org.jboss.dashboard.provider.DataProviderImpl] (ServerService Thread Pool -- 55) Error serializing data provider: null: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'bpms.processinstancelog' doesn't exist

...

15:06:11,646 ERROR [org.jboss.dashboard.dataset.sql.SQLDataSet] (ServerService Thread Pool -- 55) Error in load() SQLDataset. SQL = select total.processname, coalesce(total.instances,0) total, coalesce(active.instances_act,0) active, coalesce(completed.instances_compl,0) completed, coalesce(pending.instances_pend,0) pending, coalesce(suspended.instances_susp,0) suspended, coalesce(aborted.instances_abrt,0) aborted

To reproduce:
1.) Download BPMS 6 ER2 and merge it with JBoss EAP 6.1.
2.) Setup user guest, with password guest. Hint:
guest=b5d048a237bfd2874b6928e1f37ee15e
guest=kie-user,ADMIN
3.) Configure both business-central.war and dashbuilder.war to use MySQL database. Add mysql-connector-java-5.1.26-bin.jar and mysql-ds.xml to ${EAP_DIR}/standalone/deployments to deploy a MySQL datasource. Change DS name to java:jboss/datasources/mysqlDS and hibernate dialect to org.hibernate.dialect.MySQL5InnoDBDialect in dashbuilder.war/WEB-INF/jboss-web.xml and business-central.war/WEB-INF/classes/META-INF/persistence.xml.
4.) Run it with
cd ${EAP_DIR}/bin
./standalone.sh

My environment:
BPMS 6 ER2
JBoss EAP 6.1
MySQL 5.5.32
mysql-connector-java-5.1.26-bin.jar driver

Comment 1 Jiri Svitak 2013-09-04 13:23:27 UTC
Created attachment 793668 [details]
mysql-ds.xml

Please setup your local database to match information in this data source.

Comment 2 David Gutierrez 2013-09-09 10:49:12 UTC
Those kind of errors are raised when the jbpm-dashboard is NOT deployed right after kie-wb. Please, review the deployment order and ensure the jBPM database schema is available before deploying the jbpm-dashboard as explained here:

 https://github.com/droolsjbpm/jbpm-dashboard/blob/master/jbpm-dashboard-distributions/src/main/jbossas7/README.md)

Comment 6 Jiri Svitak 2013-10-18 13:59:24 UTC
According to steps mentioned by David, this is not a bug, but a product feature. User needs to follow the specific deployment steps to make sure such errors are not thrown.

Closing as this won't be changed.