Bug 983534

Description of problem:

When dashbuilder and business-central are deployed together, dashbuilder creates 2 tables shared by both applications, even though the table creation should have been left to business central (see comment 3 in this bug https://bugzilla.redhat.com/show_bug.cgi?id=973132#c3).

(1) There is an error in JBoss EAP application log when deploying dashbuilder together with business-central:

13:14:38,460 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (ServerService Thread Pool -- 57) HHH000388: Unsuccessful: create table BAMTaskSummary (pk int8 not null, createdDate timestamp, duration int8, endDate timestamp, processInstanceId int8 not null, startDate timestamp, status varchar(255), taskId int8 not null, taskName varchar(255), userId varchar(255), primary key (pk))
13:14:38,461 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (ServerService Thread Pool -- 57) ERROR: relation "bamtasksummary" already exists
13:14:43,042 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (ServerService Thread Pool -- 57) HHH000388: Unsuccessful: create table ProcessInstanceLog (id int8 not null, duration int8, end_date timestamp, externalId varchar(255), user_identity varchar(255), outcome varchar(255), parentProcessInstanceId int8, processId varchar(255), processInstanceId int8 not null, processName varchar(255), processVersion varchar(255), start_date timestamp, status int4, primary key (id))
13:14:43,042 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (ServerService Thread Pool -- 57) ERROR: relation "processinstancelog" already exists



(2) From dashbuilder application log we can see, that the tables were obviously created by dashbuilder:

[ServerService Thread Pool -- 60 11/07/13 13:14:20] WARN  org.jboss.dashboard.database.DatabaseAutoSynchronizer (DatabaseAutoSynchronizer.java:91) - Running file 1-create-postgres.sql []
[ServerService Thread Pool -- 60 11/07/13 13:14:28] WARN  org.jboss.dashboard.database.DatabaseAutoSynchronizer (DatabaseAutoSynchronizer.java:91) - Running file 2-jbpm-historylog-postgres.sql []

------------------

Version-Release number of selected component (if applicable):
BPMS 6.0.0.DR6
http://jawa05.englab.brq.redhat.com/candidate/BPMS-6.0.0-DR6/
-->  bpms-6.0.0.Beta-redhat-1-bpms-eap6.zip deployed on JBoss EAP 6.1

How reproducible:
Configure EAP 6.1 to use PostgreSQL datasource
+ specify <property name="hibernate.dialect" value="org.hibernate.dialect.PostgreSQLDialect" />

Steps to Reproduce:
1. Configure EAP 6.1 to use PostgreSQL datasource
2. Configure business-central to use this datasource (Set org.hibernate.dialect.PostgreSQLDialect as hibernate.dialect in business-central.war   -> persistence.xml)
3. Configure dashbuilder to use this datasource (based on info from engineering, it is enough to put line with postgresql module in jboss-deployment structure - see https://github.com/droolsjbpm/dashboard-builder/blob/master/builder/src/main/jbossas7/README.md)
4. Start the EAP

Actual results:
The error (1) above apears in the application server startup log, because the 2 tables are created by dashboard builder, not by console.

Expected results:
No errors while deploying the 2 apps together.

Additional info: