[MGNLWORKFLOW-331] Scheduled publication won't executed after Tomcat restart Created: 20/Apr/16 Updated: 20/Apr/16 Resolved: 20/Apr/16 |
|
| Status: | Closed |
| Project: | Magnolia Workflow Module |
| Component/s: | jBPM |
| Affects Version/s: | 5.4.8 |
| Fix Version/s: | 5.5 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Frank Sommer | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | workflow | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||
| Date of First Response: | |||||
| Description |
|
If you schedule a publication and restart the server before the publication date is reached, the activation won't be executed. The workflow process is still active, but won't be triggered to be executed. In Magnolia 5.4.x with workflow 5.5.1 it seems to work. |
| Comments |
| Comment by Richard Gange [ 20/Apr/16 ] |
|
The issue is due to the underlying timer used by the workflow not being designed to persist. See https://issues.jboss.org/browse/JBPM-4794. Workarounds:
|