[ 
http://jira.magnolia.info/browse/MAGNOLIA-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17414#action_17414
 ] 

Jan Haderka commented on MAGNOLIA-1142:
---------------------------------------

as of 3.6.1:
- if participant can't be found or fails during execution, the error is logged
{code}
INFO   openwfe.org.embed.impl.engine.AbstractEmbeddedParticipant 
MgnlParticipant.java(consume:111) 07.08.2008 09:45:39  consume command 
command-logWorkItem...
ERROR  openwfe.org.embed.impl.engine.AbstractEmbeddedParticipant 
MgnlParticipant.java(consume:135) 07.08.2008 09:45:39  No command has been 
found through the magnolia catalog for name: command-logWorkItem
INFO   openwfe.org.embed.impl.engine.AbstractEmbeddedParticipant 
MgnlParticipant.java(consume:138) 07.08.2008 09:45:39  consume command 
command-logWorkItem end
{code}

- there is not ATTRIBUTE_EXCEPTION nor is there any CommandNotFoundException
- actually correct behaviour in this case seems to indeed leave item stalled 
since this is what OpenWFE does normally when failing to execute participant. 
See [1] for details. The else-ref or default timeout in the workflow can take 
care of resuming execution should one of the participants fail. Alternativally 
such stalled workflow can be resumed or removed manually.

[1] 
http://www.nabble.com/-owfe-users--correct-response-from-participant-in-event-of-failure--td7356870.html

> workflow probably stalled if command referenced by magnolia command 
> participant is not found
> --------------------------------------------------------------------------------------------
>
>                 Key: MAGNOLIA-1142
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-1142
>             Project: Magnolia
>          Issue Type: Bug
>            Reporter: Chris Miner
>            Assignee: Boris Kraft
>
> i created a workflow with a command participant:
>               <participant ref="command-logWorkItem"/>
> logWorkItem doesn't exist in any catalog of commands.  And it doesn't exist 
> in the catalog named 'default'.  Stepping through the code in 
> MgnlParticipant, I am not sure it does the right thing in that case.  
> Specifically no reply to the engine is done.  I think this would leave the 
> item 'stalled'.  Probably a failure to find the command should result in the 
> item being rejected.

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

Reply via email to