Unable to start Flowable 6.3.0 with Postgresql 9.6

Flowable Engine
1

Hi,

I have downloaded flowable-6.3.0.zip, run the db script flowable.postgres.all.create.sql in postgresql 9.6,
modified application.properties for flowable-admin.war, flowable-idm.war, flowable-modeler.war, flowable-rest.war and flowable-task.war as floowing,

#spring.datasource.driver-class-name=org.h2.Driver
#spring.datasource.url=jdbc:h2:tcp://localhost/flowableadmin
#spring.datasource.url=jdbc:h2:~/flowable-db/db;AUTO_SERVER=TRUE;AUTO_SERVER_PORT=9091;DB_CLOSE_DELAY=-1

#spring.datasource.driver-class-name=com.mysql.jdbc.Driver
#spring.datasource.url=jdbc:mysql://127.0.0.1:3306/flowable?characterEncoding=UTF-8

spring.datasource.driver-class-name=org.postgresql.Driver
spring.datasource.url=jdbc:postgresql://localhost:5432/flowable

Deployed war into tomcat 8.5.30. Only flowable-admin and flowable-modler able to start,
flowable-idm.war, flowable-task.war and flowable-rest.war failed to start due to following error.

2018-05-09 12:19:03,041 [localhost-startStop-1] ERROR org.flowable.engine.common.impl.db.AbstractSqlScriptBasedDbSchemaManager - Could not get property from table ACT_ID_PROPERTY
org.postgresql.util.PSQLException: ERROR: permission denied for relation act_id_property
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2433)

I have checked flowable database, the table is exists.

Any idea why still not able to read ACT_ID_PROPERTY table even though it is exist?

2

Have you checked that the user has permissions to see the table?
I’ve also encountered that (depending on your configuration) the engine is looking in the public schema instead of the one you designated.
At one point we had set up a user for flowable that has our flowable schema as it’s default instead of the public schema.
Hope this helps.

3

@Tony-C if you are manually installing the SQL you would need to disable the automatic update from Flowable. You can do that by setting flowable.database-schema-update=ignore

4

@maudrid, Thank you so much. Indeed it is the user permission issue. I have fixed and it is working now. It is very helpful!

5

@filiphr, Thanks for your tips to disable automatic schema update.