[ http://jira.magnolia.info/browse/MAGNOLIA-1982?page=all ]

Grégory Joseph updated MAGNOLIA-1982:
-------------------------------------

     Attachment: MAGNOLIA-1982_stacktrace.txt
    Description: 
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..

  was:
Sometimes when we try to activate a page in our Magnolia authoring instance 
this results in the following error:

"
INFO   | jvm 1    | 2007/12/14 16:28:13 | ERROR  
info.magnolia.module.workflow.WorkflowUtil
WorkflowUtil.java(launchFlow:80) 14.12.2007 16:28:13  Launching fl ow failed
INFO   | jvm 1    | 2007/12/14 16:28:13 | 
openwfe.org.engine.launch.LaunchException: launch failed
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
openwfe.org.engine.impl.launch.SimpleXmlLauncher.launch(SimpleXmlLauncher.java:326)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
openwfe.org.engine.impl.launch.SimpleXmlLauncher.launch(SimpleXmlLauncher.java:122)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
openwfe.org.embed.impl.engine.AbstractEngine.launch(AbstractEngine.java:214)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.module.workflow.WorkflowUtil.launchFlow(WorkflowUtil.java:77)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.module.workflow.WorkflowUtil.launchFlow(WorkflowUtil.java:118)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.module.workflow.commands.FlowCommand.execute(FlowCommand.java:57)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.commands.MgnlCommand.executePooledOrSynchronized(MgnlCommand.java:141)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.commands.MgnlCommand.execute(MgnlCommand.java:128)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:190)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.servlets.CommandBasedMVCServletHandler.execute(CommandBasedMVCServletHandler.java:78)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.servlets.MVCServlet.doPost(MVCServlet.java:111)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MagnoliaManagedFilter$CustomFilterChain.doFilter(MagnoliaManagedFilter.java:88)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MgnlCmsFilter.doFilter(MgnlCmsFilter.java:106)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MagnoliaManagedFilter$CustomFilterChain.doFilter(MagnoliaManagedFilter.java:92)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.cache.CacheFilter.doFilter(CacheFilter.java:96)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MagnoliaManagedFilter$CustomFilterChain.doFilter(MagnoliaManagedFilter.java:92)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MgnlInterceptFilter.doFilter(MgnlInterceptFilter.java:130)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MagnoliaManagedFilter$CustomFilterChain.doFilter(MagnoliaManagedFilter.java:92)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MgnlContextFilter.doFilter(MgnlContextFilter.java:45)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MagnoliaManagedFilter$CustomFilterChain.doFilter(MagnoliaManagedFilter.java:92)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MultipartRequestFilter.doFilter(MultipartRequestFilter.java:80)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MagnoliaManagedFilter$CustomFilterChain.doFilter(MagnoliaManagedFilter.java:92)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MgnlVirtualUriFilter.doFilter(MgnlVirtualUriFilter.java:83)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MagnoliaManagedFilter$CustomFilterChain.doFilter(MagnoliaManagedFilter.java:92)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.security.SecurityFilter.doFilter(SecurityFilter.java:101)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MagnoliaManagedFilter$CustomFilterChain.doFilter(MagnoliaManagedFilter.java:92)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.ContentTypeFilter.doFilter(ContentTypeFilter.java:66)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MagnoliaManagedFilter$CustomFilterChain.doFilter(MagnoliaManagedFilter.java:92)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
info.magnolia.cms.filters.MagnoliaManagedFilter.doFilter(MagnoliaManagedFilter.java:65)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
INFO   | jvm 1    | 2007/12/14 16:28:13 |       at 
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773)
"

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..


(moved the stacktrace to an attachment for readability)

> 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
----------------------------------------------------------------

Reply via email to