Just downloaded 3.0.2 WARs, reconfigured to use the nosearch configurations, let them bootstrap, and got the same errors. Also tried with 3.0.3, with the same result.
Some more fooling around shows that the magnolia.properties file requires a config file that uses search. However, the repositories.xml doesn't. Curious. I think I've got things pretty well sorted out now, though I'm still curious as to why magnolia.proprties needs searching turned on. Sean On 8/28/07 2:20 PM, "Amir Mistric" <[email protected]> wrote: > Hmmm > > If you take a "clean" WAR and bootstrap it freshly without search index > configured - do you still get the errors? > If so then Magnolia is using search index internally or this is a bug. > > > Thanks > > Amir > > >> -----Original Message----- >> From: [email protected] [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, August 28, 2007 3:11 PM >> To: [email protected] >> Subject: [magnolia-user] Turning of Search Indexing >> >> Hi Folks, >> >> Our Magnolia installation has been running under an >> increasingly heavy load lately. Since we're not actually >> using Magnolia's built in search functions, I decided that a >> good way to lessen that load a bit is to turn off search indexing. >> >> Accordingly, I deleted the <SearchIndex> block from our >> repository configuration file. However, when I start up >> Magnolia without it, I start seeing lots of these in the logs: >> >> ERROR info.magnolia.context.SessionStore >> SessionStore.java(getHierarchyManager:129) 28.08.2007 >> 14:02:45 no search manager configured for this workspace >> javax.jcr.RepositoryException: no search manager configured >> for this workspace >> at >> org.apache.jackrabbit.core.WorkspaceImpl.getQueryManager(Works >> paceImpl.java: >> 569) >> at >> info.magnolia.context.SessionStore.getQueryManager(SessionStor >> e.java:204) >> at >> info.magnolia.context.SessionStore.getHierarchyManager(Session >> Store.java:123 >> ) >> ...etc... >> >> My question, then, is how to convince Magnolia to stop >> looking for a search manager altogether and thus get rid of >> these error messages. Is there another bit of configuration >> that I've missed somewhere? I'd like to have a clean log file >> so that the only ERROR messages are ones I should actually >> pay attention to! >> >> Thanks in advance for any help, >> Sean >> >> >> ---------------------------------------------------------------- >> for list details see >> http://documentation.magnolia.info/docs/en/editor/stayupdated.html >> ---------------------------------------------------------------- >> > > > ---------------------------------------------------------------- > for list details see > http://documentation.magnolia.info/docs/en/editor/stayupdated.html > ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
