Flowable Task down!

GauCho · June 12, 2020, 11:59am

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 ?

GauCho · June 15, 2020, 4:34am

We found the issue as below

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

Any suggestions ?

jorge.mora · June 18, 2020, 7:40pm

@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?

GauCho · June 19, 2020, 6:18am

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

jorge.mora · June 19, 2020, 7:13am

Ok, Gaurav.

Just post here any additional info.

Regards,
Jorge.

aashi · August 11, 2020, 4:43pm

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

jorge.mora · August 11, 2020, 8:29pm

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.

aashi · August 11, 2020, 8:46pm

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

Regards,
Ashmita Sinha

GauCho · September 3, 2020, 10:18am

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.

jorge.mora · September 3, 2020, 12:09pm

@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 .

GauCho · September 3, 2020, 12:24pm

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.

jorge.mora · September 3, 2020, 12:27pm

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.

GauCho · September 3, 2020, 12:28pm

Hi Jorge,

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

Regards,
Gaurav

jorge.mora · September 3, 2020, 12:41pm

Sure. Very easy. Just follow this link.

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.

GauCho · September 4, 2020, 4:19am

Hi Jorge,

GitHub issue raised.

Regards,
Gaurav.

jorge.mora · September 11, 2020, 7:11am

@GauCho, please, have a look at this solution. If you don’t need the event registry, maybe it’s a good workaround.

GauCho · September 11, 2020, 7:31am

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

Topic		Replies	Views
Unable to start flowable task and rest after upgrade	1	727	March 10, 2020
Spring Flowable boot failed to start Flowable Engine	0	1443	February 4, 2019
Flowable-rest.war and task is not deployed	0	736	July 30, 2019
Migration from Activiti 5.22 to Flowable 6.6.0 Flowable Engine	0	251	September 8, 2021
Flowable version upgrade issue Flowable Engine	3	1127	November 9, 2020

Flowable Task down!

Related topics