# Flowable Task down!

**URL:** <https://forum.flowable.org/t/flowable-task-down/6204>\
**Category:** Flowable Engine\
**Created:** [June 12, 2020, 11:59am UTC](https://forum.flowable.org/t/flowable-task-down/6204 "2020-06-12T11:59:32Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![GauCho](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@GauCho](https://forum.flowable.org/u/GauCho)\
**Post date:** [June 12, 2020, 11:59am UTC](https://forum.flowable.org/t/flowable-task-down/6204/1 "2020-06-12T11:59:32Z")

</div>

Hello All,

After the upgrade of flowable to 6.5, flowable task and flowable rest are not coming up.

Below is the log.

2020-06-12 13:07:04.408 WARN 12819 — [io2-443-exec-31] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Unable to start web server; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘servletEndpointRegistrar’ defined in class path resource [org/springframework/boot/actuate/autoconfigure/endpoint/web/ServletEndpointManagementContextConfiguration$WebMvcServletEndpointManagementContextConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.endpoint.web.ServletEndpointRegistrar]: Factory method ‘servletEndpointRegistrar’ threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘processEngineEndpoint’ defined in class path resource [org/flowable/spring/boot/EndpointAutoConfiguration.class]: Unsatisfied dependency expressed through method ‘processEngineEndpoint’ parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘processEngine’ defined in class path resource [org/flowable/spring/boot/ProcessEngineServicesAutoConfiguration$AlreadyInitializedAppEngineConfiguration.class]: Unsatisfied dependency expressed through method ‘processEngine’ parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘flowableAppEngine’: FactoryBean threw exception on object creation; nested exception is org.flowable.common.engine.api.FlowableException: Error initialising eventregistry data model

Has anyone encountered this ?

---

<div class="post-metadata">

**Author:** ![GauCho](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@GauCho](https://forum.flowable.org/u/GauCho)\
**Post date:** [June 15, 2020, 4:34am UTC](https://forum.flowable.org/t/flowable-task-down/6204/2 "2020-06-15T04:34:42Z")

</div>

We found the issue as below

Caused by: liquibase.exception.ValidationFailedException: Validation Failed:

Any suggestions ?

---

<div class="post-metadata">

**Author:** ![jorge.mora](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/jorge.mora/32/694_2.png) [@jorge.mora](https://forum.flowable.org/u/jorge.mora)\
**Post date:** [June 18, 2020, 7:40pm UTC](https://forum.flowable.org/t/flowable-task-down/6204/3 "2020-06-18T19:40:15Z")

</div>

@GauCho, that error shows that liquibase has found a incongruent database changeset signatures. Could it be that the migration process was stopped abruptly? Also, only one line of stacktrace is not helping too much… Can you provide more information?

---

<div class="post-metadata">

**Author:** ![GauCho](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@GauCho](https://forum.flowable.org/u/GauCho)\
**Post date:** [June 19, 2020, 6:18am UTC](https://forum.flowable.org/t/flowable-task-down/6204/4 "2020-06-19T06:18:47Z")

</div>

Hi Jorge,

We were performing test upgrade and for that we copied whole of our environment on a new host and then tried to perform the upgrade. After upgrade we had this issue.

I cant provide further logs as server is now dismantled and I would be performing an upgrade from scratch.

I will keep this thread open and update this if the issue still persists.

Regards,  
Gaurav

---

<div class="post-metadata">

**Author:** ![jorge.mora](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/jorge.mora/32/694_2.png) [@jorge.mora](https://forum.flowable.org/u/jorge.mora)\
**Post date:** [June 19, 2020, 7:13am UTC](https://forum.flowable.org/t/flowable-task-down/6204/5 "2020-06-19T07:13:36Z")

</div>

Ok, Gaurav. 👌

Just post here any additional info. 👍

Regards,  
Jorge.

---

<div class="post-metadata">

**Author:** ![aashi](https://avatars.discourse-cdn.com/v4/letter/a/da6949/32.png) [@aashi](https://forum.flowable.org/u/aashi)\
**Post date:** [August 11, 2020, 4:43pm UTC](https://forum.flowable.org/t/flowable-task-down/6204/6 "2020-08-11T16:43:44Z")

</div>

Hello,

I’ve got a similar issue on upgrading Flowable version from 6.4.1 to 6.5.0.

Did you find any solution?

Regards,  
Ashmita Sinha

---

<div class="post-metadata">

**Author:** ![jorge.mora](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/jorge.mora/32/694_2.png) [@jorge.mora](https://forum.flowable.org/u/jorge.mora)\
**Post date:** [August 11, 2020, 8:29pm UTC](https://forum.flowable.org/t/flowable-task-down/6204/7 "2020-08-11T20:29:05Z")

</div>

The error from @GauCho looks like a problem creating the tables for the event registry engine. I’d check if the database connection used by Flowable has the correct DDL permissions.

---

<div class="post-metadata">

**Author:** ![aashi](https://avatars.discourse-cdn.com/v4/letter/a/da6949/32.png) [@aashi](https://forum.flowable.org/u/aashi)\
**Post date:** [August 11, 2020, 8:46pm UTC](https://forum.flowable.org/t/flowable-task-down/6204/8 "2020-08-11T20:46:43Z")

</div>

Please share the details as well about the configuration which needs to be done.

Regards,  
Ashmita Sinha

---

<div class="post-metadata">

**Author:** ![GauCho](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@GauCho](https://forum.flowable.org/u/GauCho)\
**Post date:** [September 3, 2020, 10:18am UTC](https://forum.flowable.org/t/flowable-task-down/6204/9 "2020-09-03T10:18:39Z")

</div>

Hi All,

I tried to upgade again and it failed.

2020-09-03 12:03:42.130 WARN 1977 — [o2-443-exec-131] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Unable to start web server; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘servletEndpointRegistrar’ defined in class path resource [org/springframework/boot/actuate/autoconfigure/endpoint/web/ServletEndpointManagementContextConfiguration$WebMvcServletEndpointManagementContextConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.endpoint.web.ServletEndpointRegistrar]: Factory method ‘servletEndpointRegistrar’ threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘processEngineEndpoint’ defined in class path resource [org/flowable/spring/boot/EndpointAutoConfiguration.class]: Unsatisfied dependency expressed through method ‘processEngineEndpoint’ parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘processEngine’ defined in class path resource [org/flowable/spring/boot/ProcessEngineServicesAutoConfiguration$AlreadyInitializedAppEngineConfiguration.class]: Unsatisfied dependency expressed through method ‘processEngine’ parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘flowableAppEngine’: FactoryBean threw exception on object creation; nested exception is org.flowable.common.engine.api.FlowableException: Error initialising eventregistry data model

2020-09-03 12:03:42.132 INFO 1977 — [o2-443-exec-131] o.s.s.c.ThreadPoolTaskExecutor : Shutting down ExecutorService ‘applicationTaskExecutor’

2020-09-03 12:03:42.132 INFO 1977 — [o2-443-exec-131] c.z.h.HikariDataSource : flowable-rest - Shutdown initiated…

2020-09-03 12:03:42.147 INFO 1977 — [o2-443-exec-131] c.z.h.HikariDataSource : flowable-rest - Shutdown completed.

Above is the trace.

Also, below is the insert from the update sql

more flowable.mysql.upgradestep.6.4.2.to.6.5.0.all.sql | grep 7:d168de628476556968549f4a355baacb  
INSERT INTO ACT\_CMMN\_DATABASECHANGELOG (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRIPTION, COMMENTS, EXECTYPE, CONTEXTS, LABELS, LIQUIBASE, DEPLOYMENT\_ID) VALUES (‘8’, ‘flowable’, ‘org/flowable/cmmn/db/liquibase/flowable-cmmn-db-changelog.xml’, NOW(), 8, ‘7:d168de628476556968549f4a355baacb’, ‘addColumn tableName=ACT\_CMMN\_HI\_PLAN\_ITEM\_INST’, ‘’, ‘EXECUTED’, NULL, NULL, ‘3.5.3’, ‘9678004051’);

here its trying to add the new checksum but previous checksum was different.

---

<div class="post-metadata">

**Author:** ![jorge.mora](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/jorge.mora/32/694_2.png) [@jorge.mora](https://forum.flowable.org/u/jorge.mora)\
**Post date:** [September 3, 2020, 12:09pm UTC](https://forum.flowable.org/t/flowable-task-down/6204/10 "2020-09-03T12:09:28Z")

</div>

@GauCho, can you attach the full log file from the start? It looks like something happened to the execution of the upgrade SQL scripts (I assume that you are executing them manually). Please, also attach a dump of the Event registry DATABASECHANGELOG tables .

---

<div class="post-metadata">

**Author:** ![GauCho](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@GauCho](https://forum.flowable.org/u/GauCho)\
**Post date:** [September 3, 2020, 12:24pm UTC](https://forum.flowable.org/t/flowable-task-down/6204/11 "2020-09-03T12:24:11Z")

</div>

> [@jorge.mora](#):
>
> you attach the full log file from the start? It looks like something happened to the execution of the upgrade SQL scripts (I assume that you are executing them manually). Please, also attach a dump of the Event registry DATABASECHANGELOG tables

Hi Jorge,

Sorry, its productive system so I had to restore back. what I noticed is in table ACT\_CMMN\_DATABASECHANGELOG and FLW\_EV\_DATABASECHANGELOG, we already had entry with different checksum (MD5SUM).  
Yes, i am giving the file flowable.mysql.upgradestep.6.4.2.to.6.5.0.all.sql as an input to mysql manually. Shouldn’t we do that ?  
mysql -u -p -D database name \< flowable.mysql.upgradestep.6.4.2.to.6.5.0.all.sql

Also, the create/alter statements mentioned in the file flowable.mysql.upgradestep.6.4.2.to.6.5.0.all.sql doesn’t work as those tables/columns are already present.

Below is the flowable.mysql.upgradestep.6.4.2.to.6.5.0.all.sql file entries.

update ACT\_GE\_PROPERTY set VALUE\_ = ‘6.5.0.6’ where NAME\_ = ‘common.schema.version’;

update ACT\_GE\_PROPERTY set VALUE\_ = ‘6.5.0.6’ where NAME\_ = ‘entitylink.schema.version’;

alter table ACT\_HI\_IDENTITYLINK add column SUB\_SCOPE\_ID\_ varchar(255);

create index ACT\_IDX\_HI\_IDENT\_LNK\_SUB\_SCOPE on ACT\_HI\_IDENTITYLINK(SUB\_SCOPE\_ID\_, SCOPE\_TYPE\_);

alter table ACT\_RU\_IDENTITYLINK add column SUB\_SCOPE\_ID\_ varchar(255);

create index ACT\_IDX\_IDENT\_LNK\_SUB\_SCOPE on ACT\_RU\_IDENTITYLINK(SUB\_SCOPE\_ID\_, SCOPE\_TYPE\_);

update ACT\_GE\_PROPERTY set VALUE\_ = ‘6.5.0.6’ where NAME\_ = ‘identitylink.schema.version’;

update ACT\_GE\_PROPERTY set VALUE\_ = ‘6.5.0.6’ where NAME\_ = ‘job.schema.version’;

create table FLW\_RU\_BATCH (  
ID\_ varchar(64) not null,  
REV\_ integer,  
TYPE\_ varchar(64) not null,  
SEARCH\_KEY\_ varchar(255),  
SEARCH\_KEY2\_ varchar(255),  
CREATE\_TIME\_ datetime(3) not null,  
COMPLETE\_TIME\_ datetime(3),  
STATUS\_ varchar(255),  
BATCH\_DOC\_ID\_ varchar(64),  
TENANT\_ID\_ varchar(255) default ‘’,  
primary key (ID\_)  
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE utf8\_bin;

create table FLW\_RU\_BATCH\_PART (  
ID\_ varchar(64) not null,  
REV\_ integer,  
BATCH\_ID\_ varchar(64),  
TYPE\_ varchar(64) not null,  
SCOPE\_ID\_ varchar(64),  
SUB\_SCOPE\_ID\_ varchar(64),  
SCOPE\_TYPE\_ varchar(64),  
SEARCH\_KEY\_ varchar(255),  
SEARCH\_KEY2\_ varchar(255),  
CREATE\_TIME\_ datetime(3) not null,  
COMPLETE\_TIME\_ datetime(3),  
STATUS\_ varchar(255),  
RESULT\_DOC\_ID\_ varchar(64),  
TENANT\_ID\_ varchar(255) default ‘’,  
primary key (ID\_)  
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE utf8\_bin;

create index FLW\_IDX\_BATCH\_PART on FLW\_RU\_BATCH\_PART(BATCH\_ID\_);

alter table FLW\_RU\_BATCH\_PART  
add constraint FLW\_FK\_BATCH\_PART\_PARENT  
foreign key (BATCH\_ID\_)  
references FLW\_RU\_BATCH (ID\_);

insert into ACT\_GE\_PROPERTY values (‘batch.schema.version’, ‘6.5.0.6’, 1);

alter table ACT\_HI\_TASKINST add column PROPAGATED\_STAGE\_INST\_ID\_ varchar(255);

alter table ACT\_RU\_TASK add column PROPAGATED\_STAGE\_INST\_ID\_ varchar(255);

update ACT\_GE\_PROPERTY set VALUE\_ = ‘6.5.0.6’ where NAME\_ = ‘task.schema.version’;

update ACT\_GE\_PROPERTY set VALUE\_ = ‘6.5.0.6’ where NAME\_ = ‘variable.schema.version’;

update ACT\_GE\_PROPERTY set VALUE\_ = ‘6.5.0.6’ where NAME\_ = ‘eventsubscription.schema.version’;

alter table ACT\_RU\_EXECUTION add column REFERENCE\_ID\_ varchar(255);  
alter table ACT\_RU\_EXECUTION add column REFERENCE\_TYPE\_ varchar(255);

alter table ACT\_RU\_EXECUTION add column PROPAGATED\_STAGE\_INST\_ID\_ varchar(255);

alter table ACT\_HI\_PROCINST add column REFERENCE\_ID\_ varchar(255);  
alter table ACT\_HI\_PROCINST add column REFERENCE\_TYPE\_ varchar(255);

update ACT\_GE\_PROPERTY set VALUE\_ = ‘6.5.0.6’ where NAME\_ = ‘schema.version’;  
update ACT\_ID\_PROPERTY set VALUE\_ = ‘6.5.0.6’ where NAME\_ = ‘schema.version’;

UPDATE ACT\_APP\_DATABASECHANGELOGLOCK SET LOCKED = 1, LOCKEDBY = ‘192.168.10.1 (192.168.10.1)’, LOCKGRANTE  
D = ‘2020-01-22 08:26:43.187’ WHERE ID = 1 AND LOCKED = 0;

UPDATE ACT\_APP\_DATABASECHANGELOGLOCK SET LOCKED = 0, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1;

UPDATE ACT\_CMMN\_DATABASECHANGELOGLOCK SET LOCKED = 1, LOCKEDBY = ‘192.168.10.1 (192.168.10.1)’, LOCKGRANT  
ED = ‘2020-01-22 08:26:43.977’ WHERE ID = 1 AND LOCKED = 0;

ALTER TABLE ACT\_CMMN\_HI\_PLAN\_ITEM\_INST ADD SHOW\_IN\_OVERVIEW\_ BIT(1) NULL;

INSERT INTO ACT\_CMMN\_DATABASECHANGELOG (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRI  
PTION, COMMENTS, EXECTYPE, CONTEXTS, LABELS, LIQUIBASE, DEPLOYMENT\_ID) VALUES (‘8’, ‘flowable’, ‘org/flow  
able/cmmn/db/liquibase/flowable-cmmn-db-changelog.xml’, NOW(), 8, ‘7:d168de628476556968549f4a355baacb’, ’  
addColumn tableName=ACT\_CMMN\_HI\_PLAN\_ITEM\_INST’, ‘’, ‘EXECUTED’, NULL, NULL, ‘3.5.3’, ‘9678004051’);

ALTER TABLE ACT\_CMMN\_RU\_PLAN\_ITEM\_INST ADD EXTRA\_VALUE\_ VARCHAR(255) NULL;

ALTER TABLE ACT\_CMMN\_HI\_PLAN\_ITEM\_INST ADD EXTRA\_VALUE\_ VARCHAR(255) NULL;

INSERT INTO ACT\_CMMN\_DATABASECHANGELOG (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRI  
PTION, COMMENTS, EXECTYPE, CONTEXTS, LABELS, LIQUIBASE, DEPLOYMENT\_ID) VALUES (‘9’, ‘flowable’, ‘org/flow  
able/cmmn/db/liquibase/flowable-cmmn-db-changelog.xml’, NOW(), 9, ‘7:20048a5d52039eaabb32dbb30240fc08’, ’  
addColumn tableName=ACT\_CMMN\_RU\_PLAN\_ITEM\_INST; addColumn tableName=ACT\_CMMN\_HI\_PLAN\_ITEM\_INST’, ‘’, ‘EXE  
CUTED’, NULL, NULL, ‘3.5.3’, ‘9678004051’);

ALTER TABLE ACT\_CMMN\_RU\_CASE\_INST ADD REFERENCE\_ID\_ VARCHAR(255) NULL;

ALTER TABLE ACT\_CMMN\_RU\_CASE\_INST ADD REFERENCE\_TYPE\_ VARCHAR(255) NULL;

CREATE INDEX ACT\_IDX\_CASE\_INST\_REF\_ID\_ ON ACT\_CMMN\_RU\_CASE\_INST(REFERENCE\_ID\_);

ALTER TABLE ACT\_CMMN\_HI\_CASE\_INST ADD REFERENCE\_ID\_ VARCHAR(255) NULL;

ALTER TABLE ACT\_CMMN\_HI\_CASE\_INST ADD REFERENCE\_TYPE\_ VARCHAR(255) NULL;

INSERT INTO ACT\_CMMN\_DATABASECHANGELOG (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRI  
PTION, COMMENTS, EXECTYPE, CONTEXTS, LABELS, LIQUIBASE, DEPLOYMENT\_ID) VALUES (‘10’, ‘flowable’, ‘org/flo  
wable/cmmn/db/liquibase/flowable-cmmn-db-changelog.xml’, NOW(), 10, ‘7:e20ea59573dc2a33bbf72043ea09ea4d’,  
‘addColumn tableName=ACT\_CMMN\_RU\_CASE\_INST; addColumn tableName=ACT\_CMMN\_RU\_CASE\_INST; createIndex index  
Name=ACT\_IDX\_CASE\_INST\_REF\_ID\_, tableName=ACT\_CMMN\_RU\_CASE\_INST; addColumn tableName=ACT\_CMMN\_HI\_CASE\_INS  
T; addColumn tableName=ACT\_CMMN\_HI\_CASE…’, ‘’, ‘EXECUTED’, NULL, NULL, ‘3.5.3’, ‘9678004051’);

ALTER TABLE ACT\_CMMN\_RU\_PLAN\_ITEM\_INST ADD DERIVED\_CASE\_DEF\_ID\_ VARCHAR(255) NULL;

ALTER TABLE ACT\_CMMN\_HI\_PLAN\_ITEM\_INST ADD DERIVED\_CASE\_DEF\_ID\_ VARCHAR(255) NULL;

INSERT INTO ACT\_CMMN\_DATABASECHANGELOG (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRI  
PTION, COMMENTS, EXECTYPE, CONTEXTS, LABELS, LIQUIBASE, DEPLOYMENT\_ID) VALUES (‘11’, ‘flowable’, ‘org/flo  
wable/cmmn/db/liquibase/flowable-cmmn-db-changelog.xml’, NOW(), 11, ‘7:21c7a61ad7fb26abc675dff7ac54e43e’,  
‘addColumn tableName=ACT\_CMMN\_RU\_PLAN\_ITEM\_INST; addColumn tableName=ACT\_CMMN\_HI\_PLAN\_ITEM\_INST’, ‘’, ‘E  
XECUTED’, NULL, NULL, ‘3.5.3’, ‘9678004051’);

UPDATE ACT\_CMMN\_DATABASECHANGELOGLOCK SET LOCKED = 0, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1;

CREATE TABLE FLW\_EV\_DATABASECHANGELOGLOCK (ID INT NOT NULL, LOCKED BIT(1) NOT NULL, LOCKGRANTED datetime  
NULL, LOCKEDBY VARCHAR(255) NULL, CONSTRAINT PK\_FLW\_EV\_DATABASECHANGELOGLOCK PRIMARY KEY (ID));

DELETE FROM FLW\_EV\_DATABASECHANGELOGLOCK;

INSERT INTO FLW\_EV\_DATABASECHANGELOGLOCK (ID, LOCKED) VALUES (1, 0);

UPDATE FLW\_EV\_DATABASECHANGELOGLOCK SET LOCKED = 1, LOCKEDBY = ‘192.168.10.1 (192.168.10.1)’, LOCKGRANTED  
= ‘2020-01-22 08:26:44.423’ WHERE ID = 1 AND LOCKED = 0;

CREATE TABLE FLW\_EV\_DATABASECHANGELOG (ID VARCHAR(255) NOT NULL, AUTHOR VARCHAR(255) NOT NULL, FILENAME V  
ARCHAR(255) NOT NULL, DATEEXECUTED datetime NOT NULL, ORDEREXECUTED INT NOT NULL, EXECTYPE VARCHAR(10) NO  
T NULL, MD5SUM VARCHAR(35) NULL, DESCRIPTION VARCHAR(255) NULL, COMMENTS VARCHAR(255) NULL, TAG VARCHAR(2  
55) NULL, LIQUIBASE VARCHAR(20) NULL, CONTEXTS VARCHAR(255) NULL, LABELS VARCHAR(255) NULL, DEPLOYMENT\_ID  
VARCHAR(10) NULL);

CREATE TABLE FLW\_EVENT\_DEPLOYMENT (ID\_ VARCHAR(255) NOT NULL, NAME\_ VARCHAR(255) NULL, CATEGORY\_ VARCHAR(  
255) NULL, DEPLOY\_TIME\_ datetime(3) NULL, TENANT\_ID\_ VARCHAR(255) NULL, PARENT\_DEPLOYMENT\_ID\_ VARCHAR(255  
) NULL, CONSTRAINT PK\_FLW\_EVENT\_DEPLOYMENT PRIMARY KEY (ID\_));

CREATE TABLE FLW\_EVENT\_RESOURCE (ID\_ VARCHAR(255) NOT NULL, NAME\_ VARCHAR(255) NULL, DEPLOYMENT\_ID\_ VARCH  
AR(255) NULL, RESOURCE\_BYTES\_ LONGBLOB NULL, CONSTRAINT PK\_FLW\_EVENT\_RESOURCE PRIMARY KEY (ID\_));

CREATE TABLE FLW\_EVENT\_DEFINITION (ID\_ VARCHAR(255) NOT NULL, NAME\_ VARCHAR(255) NULL, VERSION\_ INT NULL,  
KEY\_ VARCHAR(255) NULL, CATEGORY\_ VARCHAR(255) NULL, DEPLOYMENT\_ID\_ VARCHAR(255) NULL, TENANT\_ID\_ VARCHA  
R(255) NULL, RESOURCE\_NAME\_ VARCHAR(255) NULL, DESCRIPTION\_ VARCHAR(255) NULL, CONSTRAINT PK\_FLW\_EVENT\_DE  
FINITION PRIMARY KEY (ID\_));

CREATE UNIQUE INDEX ACT\_IDX\_EVENT\_DEF\_UNIQ ON FLW\_EVENT\_DEFINITION(KEY\_, VERSION\_, TENANT\_ID\_);

CREATE TABLE FLW\_CHANNEL\_DEFINITION (ID\_ VARCHAR(255) NOT NULL, NAME\_ VARCHAR(255) NULL, VERSION\_ INT NUL  
L, KEY\_ VARCHAR(255) NULL, CATEGORY\_ VARCHAR(255) NULL, DEPLOYMENT\_ID\_ VARCHAR(255) NULL, CREATE\_TIME\_ da  
tetime(3) NULL, TENANT\_ID\_ VARCHAR(255) NULL, RESOURCE\_NAME\_ VARCHAR(255) NULL, DESCRIPTION\_ VARCHAR(255)  
NULL, CONSTRAINT PK\_FLW\_CHANNEL\_DEFINITION PRIMARY KEY (ID\_));

CREATE UNIQUE INDEX ACT\_IDX\_CHANNEL\_DEF\_UNIQ ON FLW\_CHANNEL\_DEFINITION(KEY\_, VERSION\_, TENANT\_ID\_);

INSERT INTO FLW\_EV\_DATABASECHANGELOG (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, MD5SUM, DESCRIPT  
ION, COMMENTS, EXECTYPE, CONTEXTS, LABELS, LIQUIBASE, DEPLOYMENT\_ID) VALUES (‘1’, ‘flowable’, ‘org/flowab  
le/eventregistry/db/liquibase/flowable-eventregistry-db-changelog.xml’, NOW(), 1, ‘7:0aaa7b01343f4cdaf101  
9cd2de3f98f3’, ‘createTable tableName=FLW\_EVENT\_DEPLOYMENT; createTable tableName=FLW\_EVENT\_RESOURCE; cre  
ateTable tableName=FLW\_EVENT\_DEFINITION; createIndex indexName=ACT\_IDX\_EVENT\_DEF\_UNIQ, tableName=FLW\_EVEN  
T\_DEFINITION; createTable tableName=FLW\_CHANNEL\_DEFIN…’, ‘’, ‘EXECUTED’, NULL, NULL, ‘3.5.3’, ‘96780044  
47’);

UPDATE FLW\_EV\_DATABASECHANGELOGLOCK SET LOCKED = 0, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1;

UPDATE ACT\_DMN\_DATABASECHANGELOGLOCK SET LOCKED = 1, LOCKEDBY = ‘192.168.10.1 (192.168.10.1)’, LOCKGRANTE  
D = ‘2020-01-22 08:26:44.648’ WHERE ID = 1 AND LOCKED = 0;

UPDATE ACT\_DMN\_DATABASECHANGELOGLOCK SET LOCKED = 0, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1;

UPDATE ACT\_FO\_DATABASECHANGELOGLOCK SET LOCKED = 1, LOCKEDBY = ‘192.168.10.1 (192.168.10.1)’, LOCKGRANTED  
= ‘2020-01-22 08:26:44.755’ WHERE ID = 1 AND LOCKED = 0;

UPDATE ACT\_FO\_DATABASECHANGELOGLOCK SET LOCKED = 0, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1;

UPDATE ACT\_CO\_DATABASECHANGELOGLOCK SET LOCKED = 1, LOCKEDBY = ‘192.168.10.1 (192.168.10.1)’, LOCKGRANTED  
= ‘2020-01-22 08:26:44.830’ WHERE ID = 1 AND LOCKED = 0;

UPDATE ACT\_CO\_DATABASECHANGELOGLOCK SET LOCKED = 0, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1;

the alter/create command doesn’t work.  
If I do not run the insert commands for the above two tables, the flowable task and rest would come up.

---

<div class="post-metadata">

**Author:** ![jorge.mora](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/jorge.mora/32/694_2.png) [@jorge.mora](https://forum.flowable.org/u/jorge.mora)\
**Post date:** [September 3, 2020, 12:27pm UTC](https://forum.flowable.org/t/flowable-task-down/6204/12 "2020-09-03T12:27:04Z")

</div>

Yes, probably, they would… Maybe we are talking about a bug in the upgrade Scripts, but that needs to be confirmed. Can you raise an issue in github for that? I think it’s the best way to handle this.

---

<div class="post-metadata">

**Author:** ![GauCho](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@GauCho](https://forum.flowable.org/u/GauCho)\
**Post date:** [September 3, 2020, 12:28pm UTC](https://forum.flowable.org/t/flowable-task-down/6204/13 "2020-09-03T12:28:26Z")

</div>

Hi Jorge,

Could you please guide me on how to do that ?  
Sorr, I am new to this.

Regards,  
Gaurav

---

<div class="post-metadata">

**Author:** ![jorge.mora](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/jorge.mora/32/694_2.png) [@jorge.mora](https://forum.flowable.org/u/jorge.mora)\
**Post date:** [September 3, 2020, 12:41pm UTC](https://forum.flowable.org/t/flowable-task-down/6204/14 "2020-09-03T12:41:07Z")

</div>

Sure. Very easy. Just follow this [link](https://github.com/flowable/flowable-engine/issues/new?assignees=&labels=&template=bug_report.md&title=).

In the bug template you have more instructions about how to describe the bug but most of it you already have it here, in the forum post. In fact, is a good idea to include a link to the forum post as well.

---

<div class="post-metadata">

**Author:** ![GauCho](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@GauCho](https://forum.flowable.org/u/GauCho)\
**Post date:** [September 4, 2020, 4:19am UTC](https://forum.flowable.org/t/flowable-task-down/6204/15 "2020-09-04T04:19:52Z")

</div>

Hi Jorge,

GitHub issue raised.

> <https://github.com/flowable/flowable-engine/issues/2569>
>
> Describe the bug
> After upgrade of flowable from 4.2 to 5.0 and running the upgrade SQL script flowable-task and flowable-rest stops.
> Expected behavior
> Flowable-task...

Regards,  
Gaurav.

---

<div class="post-metadata">

**Author:** ![jorge.mora](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/jorge.mora/32/694_2.png) [@jorge.mora](https://forum.flowable.org/u/jorge.mora)\
**Post date:** [September 11, 2020, 7:11am UTC](https://forum.flowable.org/t/flowable-task-down/6204/16 "2020-09-11T07:11:23Z")

</div>

@GauCho, please, have a look at [this solution](https://forum.flowable.org/t/upgrading-from-6-3-0-1-to-6-5-0-6-failing/6668/7). If you don’t need the event registry, maybe it’s a good workaround.

---

<div class="post-metadata">

**Author:** ![GauCho](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@GauCho](https://forum.flowable.org/u/GauCho)\
**Post date:** [September 11, 2020, 7:31am UTC](https://forum.flowable.org/t/flowable-task-down/6204/17 "2020-09-11T07:31:15Z")

</div>

@jorge.mora yes, seems to be a good workaround. I will implement it.