Flowable upgrade from 6.5 to 6.6

Flowable Engine
1

Hello Colleagues,

We are using flowable 6.4.2 currently. We want to move to 6.6 version

Therefore, we followed the staggered approach on our sandbox system to first upgrade it to 6.5 and then later from 6.5 to 6.6.

After performing an upgrade from version 6.5 to 6.6, we lost all the apps created in flowable. Do we need to export all the apps before upgrade and later import them? or there exists some other way of retaining the apps post upgrade.

Is this a normal behaviour? or did we miss some pre-requisite towards the upgrade?

Thanks,
Swapnil

2

No, of course not. This can only happen if you’ve been running with an in memory database that shuts down when the JDK is shut down.

3

Hello Joram,

Thanks for the reply !

We’re using MySQL as a DB

4

If you have configured Flowable to use Mysql, the data should be in the database:

  • Table ACT_DE_MODEL should contain any model (including apps)
  • Table ACT_APP_DEPLOYMENT should contain apps that are deployed to the runtime
5

Hello.

I noticed something like that, but what I found out is that the applications and the processes definitions are not “lost”, they are just not shown in the modeler app.

I don’t know why, but I can see all the information when I use the admin, but not in the modeler.

6

@joram

Hello
Is this bug (post migration), which needs a correction? As we’re not able to see apps in modeler (though they’re not lost)

7

@douglascrp and @Swapnil are you sure that the application is pointing to the correct database?

How do you DB connection properties look like?

8

@filiphr

Yes, the application was pointing to wrong database. We’ve corrected it now and the flowable works fine.

Thanks

9

@filiphr

Post upgrade to 6.6 we’re facing issues with Admin

“An error occurred while calling flowable HTTP/1.1 401”

2021-02-23 09:12:58.302 ERROR 23165 — [io2-443-exec-40] o.f.u.a.r.c.DeploymentsClientResource : Error getting deployments

org.flowable.ui.admin.service.engine.exception.FlowableServiceException: An error occurred while calling Flowable: HTTP/1.1 401
at org.flowable.ui.admin.service.engine.FlowableClientService.executeRequest(FlowableClientService.java:167) ~[flowable-ui-admin-logic-6.6.0.jar:6.6.0]
at org.flowable.ui.admin.service.engine.FlowableClientService.executeRequest(FlowableClientService.java:135) ~[flowable-ui-admin-logic-6.6.0.jar:6.6.0]
at org.flowable.ui.admin.service.engine.FlowableClientService.executeRequest(FlowableClientService.java:131) ~[flowable-ui-admin-logic-6.6.0.jar:6.6.0]
at org.flowable.ui.admin.service.engine.DeploymentService.listDeployments(DeploymentService.java:75) ~[flowable-ui-admin-logic-6.6.0.jar:6.6.0]
at org.flowable.ui.admin.rest.client.DeploymentsClientResource.listDeployments(DeploymentsClientResource.java:60) ~[flowable-ui-admin-rest-6.6.0.jar:6.6.0]
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) ~[na:na]
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]
at java.base/java.lang.reflect.Method.invoke(Method.java:564) ~[na:na]
at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190) ~[spring-web-5.2.9.RELEASE.jar:5.2.9.RELEASE]
at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138) ~[spring-web-5.2.9.RELEASE.jar:5.2.9.RELEASE]
at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:105) ~[spring-webmvc-5.2.9.RELEASE.jar:5.2.

10

@Swapnil this looks like a misconfiguration as well. You are getting HTTP 401, which means that the user you are using in Admin does not have access to the application.

11

@filiphr

The User I’m using have access to all apps Admin/Task/Modeler/IDM. Could it be any other issue?

12

@filiphr

Thanks !! The error with Admin was solved after changing credentials for the user.

Now we’re facing errors while executing models:-

2021-02-23 10:21:19.983 ERROR 23165 — [io2-443-exec-53] o.s.b.w.servlet.support.ErrorPageFilter : Forwarding to error page from request [/app/rest/process-instances/] due to exception [

Error updating database. Cause: java.sql.SQLSyntaxErrorException: Unknown column ‘TRANSACTION_ORDER_’ in ‘field list’

The error may exist in org/flowable/db/mapping/entity/HistoricActivityInstance.xml

The error may involve org.flowable.engine.impl.persistence.entity.HistoricActivityInstanceEntityImpl.bulkInsertHistoricActivityInstance-Inline

The error occurred while setting parameters

SQL: insert into ACT_HI_ACTINST ( ID_, REV_, PROC_DEF_ID_, PROC_INST_ID_, EXECUTION_ID_, ACT_ID_, TASK_ID_, CALL_PROC_INST_ID_, ACT_NAME_, ACT_TYPE_, ASSIGNEE_, START_TIME_, END_TIME_, TRANSACTION_ORDER_, DURATION_, DELETE_REASON_, TENANT_ID_ ) values (?, 1, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) , (?, 1, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)

Cause: java.sql.SQLSyntaxErrorException: Unknown column ‘TRANSACTION_ORDER_’ in ‘field list’]

org.apache.ibatis.exceptions.PersistenceException:

Error updating database. Cause: java.sql.SQLSyntaxErrorException: Unknown column ‘TRANSACTION_ORDER_’ in ‘field list’

The error may exist in org/flowable/db/mapping/entity/HistoricActivityInstance.xml

The error may involve org.flowable.engine.impl.persistence.entity.HistoricActivityInstanceEntityImpl.bulkInsertHistoricActivityInstance-Inline

The error occurred while setting parameters

SQL: insert into ACT_HI_ACTINST ( ID_, REV_, PROC_DEF_ID_, PROC_INST_ID_, EXECUTION_ID_, ACT_ID_, TASK_ID_, CALL_PROC_INST_ID_, ACT_NAME_, ACT_TYPE_, ASSIGNEE_, START_TIME_, END_TIME_, TRANSACTION_ORDER_, DURATION_, DELETE_REASON_, TENANT_ID_ ) values (?, 1, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) , (?, 1, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)

Cause: java.sql.SQLSyntaxErrorException: Unknown column ‘TRANSACTION_ORDER_’ in ‘field list’

    at org.apache.ibatis.exceptions.ExceptionFactory.wrapException(ExceptionFactory.java:30) ~[mybatis-3.5.5.jar:3.5.5]
    at org.apache.ibatis.session.defaults.DefaultSqlSession.update(DefaultSqlSession.java:199) ~[mybatis-3.5.5.jar:3.5.5]
    at org.apache.ibatis.session.defaults.DefaultSqlSession.insert(DefaultSqlSession.java:184) ~[mybatis-3.5.5.jar:3.5.5]
13

Hello, and sorry for the late response.

Well, I guess everything is right, as the environment is the same, and only the war files got replaced.
Besides that, I can see the historical data, and the already running process were still there, so I believe there is nothing wrong with the connection settings.

The only database related properties I have in place are:

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