Red Hat Bugzilla – Bug 1249260
[QE](6.1.z) Reading tasks from DB on MySQL 5.5 returns tasks with createdOn field that contains midnight time
Last modified: 2015-08-28 06:21:48 EDT
+++ This bug was initially created as a clone of Bug #1248527 +++
Description of problem:
When using MySQL 5.5 database system, reading tasks with method InternalTaskService.getActiveTasks() returns tasks that have narrowed creation time to midnight (e.g. 2015-07-23 00:00:00). Bug is probably somewhere where tasks are read from DB, because also method InternalTaskService.getActiveTasks(date) doesn't work.
Version-Release number of selected component (if applicable): 6.1.2.CR3
How reproducible: Run JUnit test LifeCycleLocalCommandBasedTest.testCompleteByActiveTasks from community repository jbpm using MySQL 5.5.
Actual results: Mentioned test fails.
Expected results: Mentioned test passes.
--- Additional comment from JBoss Product and Program Management on 2015-07-30 09:10:07 EDT ---
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
this is a mysql limitation as it does not store the milliseconds part of the time that is used to query for . Since the rest does have a difference for the query on milliseconds level the tests in most of the cases fails.
I'll enhance the test to rely on second level difference so it will satisfy all data bases.
Looks like 5.6 of mysql is adding some support for this though not sure how it will work from JPA provider as it might require some additional configuration.
Anyway, milliseconds level is not a big issue in my opinion especially for task queries.
improved test case back ported to 6..x branch
Verified by running LifeCycleLocalCommandBasedTest.testCompleteByActiveTasks on MySQL 5.5.