Postgres UI applications problem

Flowable Application
1

Hello.
When i started working with h2 database in ui applications like task, admin everything was fine.
Unfortunately, when i changed default database to postgres i could not make applications to work.
I can see that engine created tables though. I placed jdbc postgres driver also.
I think i made all correct.
My logs from Tomcat:

23-Feb-2017 11:04:17.784 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive C:\BSB\Program Files\apache-tomcat-8.5.5\webapps\flowable-idm.war
23-Feb-2017 11:04:17.784 WARNING [localhost-startStop-1] org.apache.catalina.startup.SetContextPropertiesRule.begin [SetContextPropertiesRule]{Context} Setting property ‘debug’ to ‘100’ did not find a matching property.
23-Feb-2017 11:04:20.234 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
23-Feb-2017 11:04:20.234 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/flowable-idm] startup failed due to previous errors

Finally my flowable-ui-app.properties file:

datasource.driver=org.postgresql.Driver
datasource.url=jdbc:postgresql://localhost:5432/sp?currentSchema=flowable

datasource.username=flowable
datasource.password=flowable

By the way. You also can see that engine creates tables in two different schemas in “flowable” and “public”.
I hope you will fix bugs.

2

Hi,

Yes we do bug fixes.
It doesn’t look correct that the tables are not all created in the flowable schema. Can you create a Github issue?

Best regards,

Tijs

1 Like
3

Hi,

Thanks for providing the feedback, there was indeed an issue with the DMN, Form and Content Engine when changing the schema. This should be fixed now.

Best regards,

Tijs

1 Like
4

OK. In addition [/flowable-idm] startup failed.
Great. I created issue in github.