Back to bug 801093
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Lukáš Petrovický | 2012-03-20 17:56:03 UTC | CC | lpetrovi | |
| Jiri Locker | 2012-04-02 14:24:49 UTC | Component | jBPM 5 | jBPM Console |
| Summary | Timer start event does not emit start events repeatedly | Timer start event does not emit start events repeatedly (in jBPM Console) | ||
| QA Contact | jlocker | lpetrovi | ||
| Anne-Louise Tangring | 2012-04-11 17:10:17 UTC | CC | atangrin | |
| Jiri Locker | 2012-04-12 13:26:50 UTC | QA Contact | lpetrovi | jlocker |
| Kris Verlaenen | 2012-04-13 17:00:55 UTC | Status | NEW | MODIFIED |
| Ryan Zhang | 2012-04-23 07:35:50 UTC | Status | MODIFIED | ON_QA |
| Lukáš Petrovický | 2012-05-02 10:52:59 UTC | Target Release | --- | BRMS 5.3.0.GA |
| Target Milestone | --- | ER6 | ||
| Lukáš Petrovický | 2012-06-21 05:38:11 UTC | QA Contact | jlocker | tschloss |
| Tomas Schlosser | 2012-06-21 08:37:28 UTC | Status | ON_QA | ASSIGNED |
| Maciej Swiderski | 2012-08-22 14:20:42 UTC | CC | mswiders | |
| Maciej Swiderski | 2012-08-23 14:36:46 UTC | Assignee | kverlaen | mswiders |
| Maciej Swiderski | 2012-08-30 15:40:47 UTC | See Also | https://bugzilla.redhat.com/show_bug.cgi?id=820309 | |
| Maciej Swiderski | 2012-08-31 16:28:54 UTC | Status | ASSIGNED | MODIFIED |
| Mario Fusco | 2012-08-31 18:24:01 UTC | Status | MODIFIED | ASSIGNED |
| CC | mfusco | |||
| Maciej Swiderski | 2012-09-03 14:33:40 UTC | Status | ASSIGNED | MODIFIED |
| Lukáš Petrovický | 2012-09-06 08:44:42 UTC | QA Contact | tschloss | jsvitak |
| Julian Coleman | 2012-09-11 13:05:25 UTC | Status | MODIFIED | ON_QA |
| Jiri Svitak | 2012-10-03 15:33:04 UTC | Status | ON_QA | VERIFIED |
| Maciej Swiderski | 2012-10-19 12:18:07 UTC | Doc Text | Cause: Incorrect serialization caused lost timer instances on session Consequence: after restart timers were not available Fix: Fixed serialization so timers will be properly stored Result: Timers fires properly after server restart |
|
| lcarlon | 2012-10-22 02:46:58 UTC | Doc Text | Cause: Incorrect serialization caused lost timer instances on session Consequence: after restart timers were not available Fix: Fixed serialization so timers will be properly stored Result: Timers fires properly after server restart | Incorrect serialization caused lost timers, which meant start events with a cycle time defined only started the first time and all subsequent starts were lost. This has been resolved by fixing serialization so that timers are properly stored. Start events with a cycle time interval defined, now work as expected. |
| Douglas Hoffman | 2012-11-21 06:50:22 UTC | CC | dhoffman | |
| Doc Text | Incorrect serialization caused lost timers, which meant start events with a cycle time defined only started the first time and all subsequent starts were lost. This has been resolved by fixing serialization so that timers are properly stored. Start events with a cycle time interval defined, now work as expected. | Incorrect serialization caused lost timers, which meant start events with a cycle time defined only started the first time and all subsequent starts were lost. This has been resolved by fixing serialization so that timers are properly stored. Start events with a cycle time interval defined now work as expected. | ||
| John Skeoch | 2014-10-26 20:34:59 UTC | CC | dhoffman | lcarlon |
| lcarlon | 2014-10-27 01:13:09 UTC | CC | lcarlon | |
| John Skeoch | 2015-06-02 01:39:12 UTC | QA Contact | jsvitak | mbaluch |
| PnT Account Manager | 2020-02-29 22:47:28 UTC | Assignee | mswiders | kverlaen |
| PnT Account Manager | 2020-02-29 22:57:06 UTC | CC | mswiders | |
| Jeff Fearn 🐞 | 2020-04-27 01:13:22 UTC | CC | brms-jira |
Back to bug 801093