>From looking at the log files I see that we are getting this exception
periodically as a crawler browses through our collection, and it seems to be
happening towards the end of the browse, i.e., after it's been browsing for
a while:
javax.servlet.ServletException: Servlet execution threw an exception
If I try the URL that the error complaints about later, it works just fine.
I've never tried it while the error was being generated since I check the
log files later on.
I have a script that checks for any unusual behavior, and if it detects it,
it restarts tomcat. Well, in this case it detected it and once tomcat was
restarted the error went away, and the crawler continued on without any more
errors.
Why would this be happening? It seems like some sort of resource problem or
memory issue. Also this happened in the afternoon, when no cron jobs were
running. Could this be a problem with our tomcat installation? We have a
pretty large collection ( over 33,000 items ). I can send the log file if
some one wants more details.
Many thanks!
-Jose
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
