Camunda Migration from 7.22.0 to Wildfly SNAPSHOT 7.24.0 Version Failing Timer block while Migrating using DOCKER IMAGES. #170
Unanswered
YesurajuParusu468
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Good Evening,
Previously I have used Camunda bpm docker version 7.22.0, I have attached Postgres Db to my camunda bpm docker version 7.22.0 after that i have deployed many workflows earlier, They are working and running successfully. now i want upgrade camunda to wildfly-SNAPSHOT 7.24.0. Issues facing after Upgradtion.
BEFORE
docker-compose.yaml
version: '3'
services:
camunda_worker_base:
image: camunda/camunda-bpm-platform:7.22.0
environment:
- DB_DRIVER=org.postgresql.Driver
- DB_URL=jdbc:postgresql://140.245.258.152:5432/camunda_migration_testing
- DB_USERNAME=camunda_user23
- DB_PASSWORD=ujRPrWz8rtgdSu4F
- DB_VALIDATE_ON_BORROW=true
- WAIT_FOR=140.245.258.152:5432
ports:
- "8082:8080"
volumes:
- /home/ubuntu/camunda_testing3/bpm-platform.xml:/camunda/conf/bpm-platform.xml:ro
restart: unless-stopped
networks:
- postgres
networks:
postgres:
*bpm-platform.xml

After this i have deployed workflow in it and it is running without any problem morethan 150k instances are running for that deployment.
Later Our Team Wanted Upgrade the camunda Version wildfly:SNAPSHOT version 7.24.0
AFTER
docker-compose.yaml
version: '3'
services:
camunda_worker_base:
image: camunda/camunda-bpm-platform:wildfly-SNAPSHOT
environment:
- DB_DRIVER=org.postgresql.Driver
- DB_URL=jdbc:postgresql://140.245.258.152:5432/camunda_migration_testing
- DB_USERNAME=camunda_user23
- DB_PASSWORD=ujRPrWz8rtgdSu4F
- DB_VALIDATE_ON_BORROW=true
- WAIT_FOR=140.245.258.152:5432
ports:
- "8082:8080"
volumes:
- /home/ubuntu/camunda_testing3/bpm-platform.xml:/camunda/conf/bpm-platform.xml:ro
restart: unless-stopped
networks:
- postgres
networks:
postgres:
bpm-platform.xml
DB Migrated to 7.22.0 to 7.23.0
insert into ACT_GE_SCHEMA_LOG
values ('1200', CURRENT_TIMESTAMP, '7.23.0');
alter table ACT_HI_COMMENT
add column REV_ integer not null
default 1;
alter table ACT_RU_EXECUTION add column PROC_DEF_KEY_ varchar(255);
I have upgraded db postgres version of camunda bpm 7.22.0 to 7.23.0 and changed the image to wildfly-SNAPSHOT 7.24.0 bpm version in the docker-compose.yaml and used same xml file for both versions. After doing all the above changes, all the running instances in the previous versions are camed to the new wildfly version. Then all the service tasks are executing without any error in the camunda but the all the previous running instances are stopped at TIMER BLOCKS , They are not moving and blocked all the instances at timer blocks in the new wildfly 7.24.0 version. What i need do here whether is there db postgres migration directly from 7.22.0 to 7.24.0 Or i need to make any changes in xml or i am not getting exactly stopped all the Timer blocks. Please give a better solution for me. I need upgrade version camunda wildfly which can handle previous deployments and process their running instances. Please provide the changes.......
I am not getting proper sql queries to upgrade directly to 7.24.0 from 7.22.0....
Beta Was this translation helpful? Give feedback.
All reactions