Hello Bojana, although I do not exactly see from the log, what is causing the search problem, the upgrade to Jahia 5 SP4 will surely help as we did major performance refactoring in our search module in that service pack.
In case you cannot upgrade right now, you may try changing the following parameter in WEB-INF\etc\config\quartz.properties to false: org.quartz.jobStore.txIsolationLevelSerializable = false If the problem you have is due to long garbage collection and running low on heap memory (you may monitor that with -verbose:gc or depending on the JDK you use the jmap tool which is shipped with the recent versions), you could try applying the code change commited in revision 20263 (see: http://article.gmane.org/gmane.comp.cms.jahia.cvs/17398). Anyway we strongly advise to switch to the latest service pack (=SP4). Regards, Benjamin PS: And on a side node, please fix your container/field declarations as you should not see any JahiaContainerSet: Structure has changed JahiaContainerSet: Definition for field ... has changed warnings in the logs. This also leads to stability and performance problems. More information about that is in the Template Developer Guide under section Declaration Scope. _______________________________________________ template_list mailing list [email protected] http://lists.jahia.org/cgi-bin/mailman/listinfo/template_list
