AnsweredAssumed Answered

Important: Activiti 5.15 and MySQL 5.6+ users

Question asked by jbarrez on Mar 24, 2014
Latest reply on Jan 30, 2015 by atifraza
Hello all,

As you probably read, we released Activiti 5.15 last Friday (http://bpmn20inaction.blogspot.com/2014/03/activiti-515-released.html).

Eager users have tried it out already (which is awesome!) and notified us that there is a bug when using MySQL 5.6+ and executing the upgrade scripts (for example http://forums.activiti.org/content/upgrade-514-515-mysql-error).

The bug is due to a combination of
1) An upgrade around MySQL timestamp precision (see 'Note for MySQL users' at http://activiti.org/userguide/index.html#creatingDatabaseTable).
2)  Not having a unit test in our QA environment where we test engine upgrades on all databases. So we did have a test for it, but not with the correct type of data that causes this bug.

So we've decided to release a 5.15.1 version shortly.

Master has been switched to this new version (https://github.com/Activiti/Activiti/commit/d9eb4f1f698eb19f39c1993d7c0e9e39f342089a), the bug has been fixed and the upgrade mechanism has been made better (https://github.com/Activiti/Activiti/commit/41a01f2dd44884a22ce314a1f22f6e3ccba61adc). And of course we've added upgrade tests to cover the bug (https://github.com/Activiti/Activiti-Upgrade/commit/83a39f1b45620494f0dbb7bf7ac105813cad2b5e).

5.15.1 will be a seamless upgrade from 5.15 and any version downwards (starting from 5.7).
We will wait a couple of days to see if any other major bug is uncovered and release it the end of this week.



TL;DR: Are you using MySQL 5.6+: don't upgrade to 5.15 yet, stick to 5.14.  Activiti 5.15.1 will be released shortly.Other databases are fine.


Sorry for any inconvenience this caused. And many thanks to the users who test-drive the Activiti releases!

Outcomes