Some good news from the UMD corner of the Fedora community: We have solved our Tomcat stuck thread problem!
- We were creating hundreds of resources at a time (the majority of which were web annotations to support our OCR searching capabilities)
- We were running the internal audit module [1]
Given that for every content write to the repository, the audit module required 2 writes to the repository, we believe that the problem stemmed from filling up the Modeshape event buffer way too rapidly for it to deal with.
To confirm that, we rebuilt our umd-fcrepo-webapp without the internal audit module (an extremely simple change [2]), and have been conducting additional batch load tests on it. So far, we have not had any stuck thread issues whatsoever, and we are closing in on completing our second batch of 500 newspaper issues.
Going forward, we are dropping the internal audit module, and are working on setting up the fcrepo-audit-triplestore [3] Camel route. We had been interested in doing this anyway; the stability and performance issue thus served as a kick in the pants to get it done! :-)
I hope our trials and tribulations of these past weeks can serve as guidance to other folks adopting Fedora 4, so that they can avoid those same pitfalls.
-Peter
--
Peter Eichman
Senior Software Developer
University of Maryland Libraries