FlowableException: Could not update Flowable database schema: unknown version from database: '6.5.0.6'

1

Need help to solve this issue which is coming after upgrading flowable dependency version from 6.4.1 to 6.5.0. Please find below the stacktrace for the same:

2020-08-06 09:00:24.696 INFO 6 — [ main] o.f.c.e.impl.db.CommonDbSchemaManager : upgrading flowable common schema from 6.5.0.1 to 6.5.0.6
2020-08-06 09:00:24.696 INFO 6 — [ main] o.f.c.e.impl.db.CommonDbSchemaManager : Upgrade needed: 6501 -> 6502. Looking for schema update resource for component ‘common’
2020-08-06 09:00:24.699 INFO 6 — [ main] o.f.c.e.impl.db.CommonDbSchemaManager : performing upgrade on common with resource org/flowable/common/db/upgrade/flowable.all.upgradestep.6501.to.6502.common.sql
‘flowableAppEngine’: FactoryBean threw exception on object creation; nested exception is org.flowable.common.engine.api.FlowableException: Could not update Flowable database schema: unknown version from database: '6.5.0.6’

On the dependency side we add the major version as 6.5.0 in build.gradle file, could any one please help to know from where this minor version (6.5.0.6 or 6.5.0.1) is getting picked up.

Below are the dependencies used:

implementation ‘org.mariadb.jdbc:mariadb-java-client:2.6.0’
implementation ‘org.flowable:flowable-spring-boot-starter:6.5.0’
implementation ‘org.flowable:flowable-spring-boot-starter-rest:6.5.0’

Thanks in advance !

2

Note that this is the database schema version, not the library version (which is 6.5.0).

From the exception, it looks like your database was already upgraded? Or do you have multiple instances booting up at once?

3

Yes, we have single shared database and multiple services getting deployed. But only 2 services failing with this issue. Rest all working fine and using schema version as 6.5.0.6 (from ACT_GE_PROPERTY)

4

Are all services updated to the 6.5.0 version? You can’t have older Flowable versions connected to the same database as newer Flowable versions.

Cheers,
Filip

5

Yes, all services are upgraded with 6.5 version.

6

Not sure how to help you further - if some services boot up and others don’t, and they all use the same library version then it doesn’t make sense. I’d double check all versions in the services. The logic is quite simple, as it only checks a number against the database number …