Hi Yann, I am working with Will! ;-)
Nice to meet you! My understanding is that I need to modify the index config file (workspace.xml) in the *webapp-name*/repositories/magnolia/workspaces/dam Folder, right? Yes, exactly, that's what I meant! Where would the master copy be located? The master copy is the "jackrabbit-bundle-*-search.xml" file, usually located in WEB-INF/config/repo-conf within a magnolia webapp. Jackrabbit takes this file as a template, and copies it to the workspace directory when a new workspace is created. Regards from Vienna, Richard Von: [email protected] [mailto:[email protected]] Im Auftrag von Yann Roth Gesendet: Mittwoch, 25. Februar 2015 08:23 An: Magnolia User-List Betreff: Re: [magnolia-user] Re: Java Process requiring 100% CPU power Hi Richard, I am working with Will! ;-) What do you mean with: Another point to mention, although I am sure you know it, is that the search index config needs to be inserted into the existing workspace.xml files (not just the master copy) in order to apply to already existing workspaces.? My understanding is that I need to modify the index config file (workspace.xml) in the *webapp-name*/repositories/magnolia/workspaces/dam Folder, right? Where would the master copy be located? Thanks Yann Am 24.02.2015 um 18:09 schrieb Unger, Richard <[email protected]<mailto:[email protected]>>: Hi Will, Hmmm... not too sure about the correct configuration. One thing I note is that you have a condition="@type='mp3'" - but "type" is not a property of DAM nodes, AFAIK. In Magnolia 5.3 the assets have a property "extension", but this is on the "jcr:content" subnode. Also since "jcr:content" is a subnode (of type "mgnl:resource") I am not sure it works to specify it as a property. So I would expect the search-config to look more like this for Magnolia 5.3 (but I haven't tried it out): <index-rule nodeType="mgnl:resource" condition="@extension = 'mp3'"> <property nodeScopeIndex="false">jcr:data</property> </index-rule> Another point to mention, although I am sure you know it, is that the search index config needs to be inserted into the existing workspace.xml files (not just the master copy) in order to apply to already existing workspaces. Regards from Vienna, Richard -----Ursprüngliche Nachricht----- Von: [email protected]<mailto:[email protected]> [mailto:user-list-owner@magnolia- cms.com<http://cms.com>] Im Auftrag von Will Scheidegger (via Magnolia Forums) Gesendet: Dienstag, 24. Februar 2015 17:23 An: Magnolia User List Betreff: [magnolia-user] Re: Java Process requiring 100% CPU power Hi Richard Long time no read! Thanks for your input and the link to the Stack Overflow page. We are facing the exact same problem... except that I did not quite understand what the original poster did to resolve it. To be absolutely sure it's the mp3 files that are messing up our Magnolia, I removed the folder containing the mp3 files, turned of Magnolia, deleted the index of the dam workspace, enabled indexing again and started magnolia back up: Everything was hunky dory again! Here's the indexer configuration that we have in use now (hopefully) but which had no effect yet. If anyone spots a problem with it, please let me know: [code] <?xml version="1.0"?> <!DOCTYPE configuration SYSTEM "http://jackrabbit.apache.org/dtd/indexing-configuration-1.2.dtd";> <configuration xmlns:nt="http://www.jcp.org/jcr/nt/1.0"; xmlns:mgnl="http://www.magnolia.info/jcr/mgnl"; xmlns:jcr="http://www.jcp.org/jcr/1.0";> <index-rule nodeType="mgnl:asset" condition="@type = 'mp3'"> <property nodeScopeIndex="false">jcr:content</property> </index-rule> <index-rule nodeType="nt:base"> <property isRegexp="true" nodeScopeIndex="false">mgnl:.*</property> <property isRegexp="true" nodeScopeIndex="false">jcr:.*</property> <property isRegexp="true">.*:.*</property> </index-rule> <index-rule nodeType="mgnl:page"> <property boost="3.0">title</property> </index-rule> </configuration> [/code] (We also tried with the mp3 rule in the last position) Thanks! -will -- Context is everything: http://forum.magnolia- cms.com/forum/thread.html?threadId=e06c637a-cf33-4005-8b87-<http://cms.com/forum/thread.html?threadId=e06c637a-cf33-4005-8b87-> bc6f59ebe7d0 ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing- lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]<mailto:[email protected]>> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]<mailto:[email protected]>> ---------------------------------------------------------------- ________________________________ ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]<mailto:[email protected]>> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
