[opencms-dev] Tomcat 5.0.16 usage

[M Butcher]

Mariano

Mariano Barcia wrote:
> Reed, Matt, all,
> 
> I'd like to share a experience we had recently with a opencms website
> using Lucene as the search engine.

Were the problems related directly to Lucene? (Could you tell?) The 
Lucene module does nor really use Xerces much, relying on the OpenCms 
API for as much as possible. However, I suppose a high volume of search 
requests could cause some slowing if the registry.xml file was being 
repeatedly parsed.

If the poor performance is directly related to the Lucene module, we'll 
see if we can do some performance tuning or add caching to speed things 
up. BTW -- which version of the Lucene module are you running?

> We discovered that Xerces v1.4.4 has serious performance and memory
> usage problems with Opencms-Lucene, which were solved when replaced by
> v2.5. Xerces v1.4.4 is the library bundled with OpenCMS v5.0.x, but so
> far the only non-2.5-compliant method we've seen is the one mentioned
> here by Reed (getOriginalEncoding). We changed that method to comply
> with v2.5 (easy, just change "getEncoding" for "getXmlEncoding") and
> everything has been working from then.
> 
> We have not had time yet to check on the CVS HEAD version of Opencms,
> maybe Opencms 5.3.1 has Xerces v2.x now ?

You should send them a patch against 5.0.1! Some of us still build out 
of the CVS release, and I suppose there is also the possibility of a 
5.0.2 release. If that's the only thing that is stopping newer versions 
of Xerces from working, then I'd rather see a fix very soon. I'm getting 
tired of seeing the same Xerces posting repeatedly appear on the list. ;-)

Thanks,

Matt