On May 25, 2011, at 3:12 PM, Nils Breunese wrote:
> > Jan Haderka wrote: > >> Briefly looked at the stacktrace. Seems to me like some workflow job ended >> up with error that was serialized into the workflow context and now workflow >> engine has troubles to deserialize the exception as it tries to set its >> stackTrace. I'd suggest to purge the Store & Expressions workspaces in case >> you have no workflows running. You might want to ask Support for help with >> the purge if you haven't done it before. > > We're also seeing freshly imported content disappearing from public nodes. We > had (and still have) a lot of problems activating big trees of content, so we > started importing from XML on all nodes and the programmatically setting the > content to activated. We have tried a million different approaches to get > this content live and probably had a lot of workflows fail. Could it somehow > be the case that this workflow job which ended up with error is somehow > 'stuck' and still killing the content on our public nodes or something? depending on the workflow, but yes it is possible to get job stuck in there forever. > > We'll contact Support for purging the Store & Expressions workspaces. What do > they contain exactly? those workspaces contain serialized state of the running and terminated workflows. Removing their content will clean up internal state of workflow engine and remove all jobs no matter what their status is. The workflow definition is unaffected by this operation. Regards, Jan ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
