[Archive-access-discuss] problems with slow wayback and Tomcat - found problem but not solution

[Matjaž K. <Mat...@nu...>]

Hello again,

After running bunch of tests, tried several JVM, two Tomcat (6.35 and 7.25), etc. I think I know why Tomcat is slow.

The situation is like this:

We have WCT and Wayback 1.6.0. Because Wayback 1.6.0 doesn't works alright with XMLquery (as described before in this site - http://sourceforge.net/mailarchive/forum.php?thread_name=23CFE6A5AD05E34EBCAD84B004C313BA01F511BA1D%40LCXCLMB01.LCDS.LOC.GOV&forum_name=archive-access-discuss )
Brad made a version 1.6.1.

Version 1.6.1 works fine with XMLQUERY but has (maybe only in our server) memory leak. Within an hour JVS stays without memory (I'm talking about 20GB RAM)
Another thing - version 1.6.1 doesn't redirect (it may be that just in our implementation) to result page - it keeps saying something about resource not found.

So, I had to have 2 installations of Wayback (1.6.1 - to get date results in XML (XMLquery) and 1.6.0 - to redirect to destination.
After removing 1.6.1 form webapps Tomcat runs smoothly even if I have SOLR for indexing and it has approx. 50gb of index.

And now - the question:
Could anyone check this 1.6.1 version (http://home.us.archive.org/~brad/wayback-1.6.1RC3.tar.gz)for memory leaks and/or why it doesn't redirect as 1.6.0 used to
Or
>to make< 1.6.0. to work with XMLquery. Version 1.6.0. keeps redirecting to site just like Gina Jones mentioned in thread (link is above)

The web page which uses this code is:
http://arhiv.nuk.uni-lj.si

at the moment you cannot browse through categories (I had to remove 1.6.1) but can use fulltext index and then redirection to archived site via Wayback 1.6.0.

people, thanks in advance. I'll be glad for help and for checking the site http://arhiv.nuk.uni-lj.si

best wishes,

Matjaž