|
From: Thomas B. <Tho...@KB...> - 2008-02-21 11:48:41
|
Hi all, At the KB we are severely testing Wayback 1.2.0 at the moment. My first impression is quite positive; many new functions are added, it is quite easy to implement different modules for different access points and several indexing threads can live side by side now. I have a few questions though. First of all, I'm experiencing errors which did not occur in older versions; java.lang.OutOfMemoryError: GC overhead limit exceeded. Does anyone know how to fix this? Second; when closing down Wayback in Tomcat, the lock file for the localbdb is not erased. A restart is therefore not possible. Could this be fixed so that if the webapp is closed down, the lock file is erased? Third; with a few websites the timeline GUI is scrambled. I get a full yellow screen with on every line a mark. After scrolling down that page, the website is presented normally. This is not the case with every website. My fourth and last problem is in the configuration. I would like to do some tests using the remote NutchWAX search, but there is not a clear manual of how to implement this precisely, which beans to use for example. Does anyone have a good example for me? Keep up the good work! Wayback is really becoming a beautiful piece of software. Cheers, Thomas Beekman Technical Lead KB (National Library of the Netherlands) |