Process definition update causing deletes from act_ru_event_subscr

[tomekzaremba]

Hi,

I met following problem:
1. My process is in version A and I start process instance
2. Process is waiting for message event (I see that corresponding row exists in act_ru_event_subscr)
3. I restart my application and deploy new version of process (say version B)
4. After app is started I see that started process instance is still active, but row from act_ru_event_subscr was deleted, so it can't be continued.

Is it normal behavior? I was expecting that I will be able to continue started process instance with old definition.

[tomekzaremba]

I found this thread: https://forums.activiti.org/content/subscribed-event-deleted-after-process-redeployed - author mentioned MySQL and I use PostgreSQL and have the same problem.

[tomekzaremba]

I see that in your JIRA ticket is resolved - when version 5.20 will be deployed into maven central repository? The newest stable version of Activiti integrated with Spring Boot still contains mentioned error:

<java>
<dependency>
<groupId>org.activiti</groupId>
<artifactId>activiti-spring-boot-starter-basic</artifactId>
<version>5.19.0.2</version>
</dependency>
</java>

[jbarrez]

Yes, we've finalized the fix yesterday.

"when version 5.20 will be deployed into maven central repository? "

Not sure yet. We're still planning what else needs to be in 5.20.

And of course the 5.19.0.2 will still have the problem, it was fixes yesterday 😉

[tomekzaremba]

But approximately - will version 5.20 be released during this month?

[srihari1]

I use Oracle and activity 5.19.0 version, same issue there. Not sure why the entries are deleting from  act_ru_event_subscr table. Someone can help if you have any fix for this.

[tomekzaremba]

Problem is already fixed in version 5.20 - release date is not known, as Joram said. For more details see  https://forums.activiti.org/content/subscribed-event-deleted-after-process-redeployed and Activiti JIRA mentioned there.

[jbarrez]

If an official release date is a problem, you can always build the snapshot yourself of course.
Not sure about the 5.20 release - we're also working very hard on the v6.

[srihari1]

Any possibility to get this fix in 5.19.0 release quickly.  we have a prod release in next Tuesday. if we go with the issue then critical data will be lost

Any help is appreciated.

[jbarrez]

No, many people have requirements like this. If this is crucial for you, you can always build a snapshot version yourself.