[ http://jira.magnolia.info/browse/MAGNOLIA-1982?page=comments#action_15487 ] Philipp Bracher commented on MAGNOLIA-1982: -------------------------------------------
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 > Launching flow failed > --------------------- > > Key: MAGNOLIA-1982 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1982 > Project: Magnolia > Issue Type: Bug > Components: activation > Affects Versions: 3.0.5 > Environment: Linux Centos 5, tomcat 5.5, jdk1.5.0_09, apache 2, > mod_jk, MySQL 5 > Reporter: Edgar Vonk > Assigned To: Philipp Bracher > Attachments: MAGNOLIA-1982_stacktrace.txt > > > Sometimes when we try to activate a page in our Magnolia authoring instance > this results in the following error: > (see attachment) > 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.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
