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

Nicolas Modrzyk resolved MAGNOLIA-1416.
---------------------------------------

    Resolution: Won't Fix

The workflow workspaces do need the search. There is no way around it, and no 
reason to not include the search in this workspace.

Note that this has nothing to do with the website workspace, which is probably 
the one you want to disable search for.

> Missing Search Index Configuration Breaks Workflow Engine
> ---------------------------------------------------------
>
>                 Key: MAGNOLIA-1416
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-1416
>             Project: Magnolia
>          Issue Type: Bug
>          Components: workflow
>    Affects Versions: 3.0.1
>         Environment: Tomcat, standard installation from War Files
>            Reporter: Claudio Greuter
>         Assigned To: Nicolas Modrzyk
>
> I Tried to configure a Magnolia Setup with the delivered "no-Search" config 
> file for Derby:
> After bootstrapping using this config file, the workflow engine seems to fail 
> with this stacktrace (message apprears two minutes after bootstrapping):
> ERROR  info.magnolia.module.workflow.jcr.JCRExpressionStore 01.03.2007 
> 16:58:08 -- contentIterator() failed to set up an iterator
> java.lang.NullPointerException
>       at 
> info.magnolia.module.workflow.jcr.JCRExpressionStore$StoreIterator.<init>(JCRExpressionStore.java:395)
>       at 
> info.magnolia.module.workflow.jcr.JCRExpressionStore.contentIterator(JCRExpressionStore.java:167)
>       at 
> openwfe.org.engine.impl.expool.SimpleExpressionPool.contentIterator(SimpleExpressionPool.java:989)
>       at 
> openwfe.org.engine.impl.expool.SimpleExpressionPool.purge(SimpleExpressionPool.java:1009)
>       at 
> openwfe.org.engine.impl.expool.SimpleExpressionPool$1.run(SimpleExpressionPool.java:192)
>       at java.util.TimerThread.mainLoop(Unknown Source)
>       at java.util.TimerThread.run(Unknown Source)
> Using a configuration that configures a lucene index file  no such error 
> occurs:
> This breaks the Activation workflow as well, so it s not possible to activate.
> For us it is necessary to disable the index, because of a nasty bug when the 
> index tries to parse corrput PDF files.

-- 
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://www.magnolia.info/en/developer.html
----------------------------------------------------------------

Reply via email to