[MAGNOLIA-1982] Launching flow failed Created: 28/Dec/07 Updated: 17/Mar/09 Resolved: 07/Jan/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 3.0.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Edgar Vonk | Assignee: | Philipp Bärfuss |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux Centos 5, tomcat 5.5, jdk1.5.0_09, apache 2, mod_jk, MySQL 5 |
||
| Attachments: |
|
| 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 |
|
Sometimes when we try to activate a page in our Magnolia authoring instance this results in the following error: For some reason the workflow cannot be activated for this content node. The workaround we use in this case is to activate the appropriate node from the JCR browser in Magnolia directly, thereby bypassing the workflow altogether. We cannot easily reproduce this issue as it occurs only on some occasions. Why we do not know.. |
| Comments |
| Comment by Magnolia International [ 28/Dec/07 ] |
|
Does it always fail for the same nodes? i.e have you ever been able to activate a node that showed this behaviour ? |
| Comment by Magnolia International [ 28/Dec/07 ] |
|
(moved the stacktrace to an attachment for readability) |
| Comment by Edgar Vonk [ 28/Dec/07 ] |
|
Thanks for the quick reply. 1/ Yes, the node has been activated and published. After changing the content of the node in Magnolia, this problem occurs. So it occurs on existing nodes. 2/ Yes, it happens for several nodes. It seems to happen more frequently after activating a tree of nodes. 3/ We have not seen other exceptions being logged. We will keep an eye out when it happens again. 4/ We have not tried it on 3.5 yet. We are currently investigating how to upgrade from 3.0.5 to 3.5.2. If you have any pointers on that maybe? |
| Comment by Magnolia International [ 28/Dec/07 ] |
|
4/ http://documentation.magnolia.info/docs/releases/3-5-2.html |
| Comment by Philipp Bracher [ 07/Jan/08 ] |
|
Doesn't seam to be related to the content (at least the stacktrace gives no evidence). Do you have a more precise stacktrace/log --> root cause other exceptions |
| Comment by Edgar Vonk [ 07/Jan/08 ] |
|
Sorry. We do not have more information at this point.. We are busy trying to upgrade to 3.5. We hope that will solve this issue. It's ok if you want to close this issue. Thanks for the help. |
| Comment by Philipp Bracher [ 07/Jan/08 ] |
|
We reopen the issue as soon we can reproduce it |