[MAGNOLIA-1416] Missing Search Index Configuration Breaks Workflow Engine Created: 01/Mar/07  Updated: 23/Jan/13  Resolved: 02/Mar/07

Status: Closed
Project: Magnolia
Component/s: workflow
Affects Version/s: 3.0.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Claudio Greuter Assignee: Nicolas Modrzyk
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Tomcat, standard installation from War Files


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

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.



 Comments   
Comment by Nicolas Modrzyk [ 02/Mar/07 ]

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.

Comment by Claudio Greuter [ 02/Mar/07 ]

ok ill set up the workflow repository with an index. However i suppose the nop-Search configuration files should be adjusted, because useing them out of the box leads to the described errors?

Comment by Claudio Greuter [ 02/Mar/07 ]

you've mentioned that the workflow workspaces need an index. i would like to manually update the workspace.xml files where needed to enable the index again. which workspaces do really need this index? thx for the help, claudio

Generated at Mon Feb 12 03:26:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.