(Posted this yesterday from another email-address but it hasn't made it thru yet)
-------------------------------------------------------- Help: Tomcat 3.3 with Cocoon 2.0 hangs(?) on SuSE Linux! -------------------------------------------------------- We are currently experiencing a PITA problem on several SuSE Linux systems (with different kernel versions) where Tomcat 3.3 will just seem to hang after a while. I am hoping someone out there has perhaps an idea what we need to examine to find out what is going on. We are using WGET to send parallel requests into Cocoon 2.0. In all there are about 4 - 6 requests being processed in parallel at any one time. The actual pipeline that is called fetches XML data from an external source and then uses the Cocoon caching mechanism to keep the data in the cache. The systems will run ok for various lengths of time (we have seen 2000-3000 requests be processed before the hang - but also seen 17000 requests before the same thing happens) before basically just stoping. There are no errors to be found in any of the logs (tomcat, Cocoon, console). Tomcat just does not respond. When looking at the vital signs of the system - what we see does not really help us to see what is going on. We are currently checking Cocoon and our additional components for memory leaks (which would seem to be the most obvious cause) but if this is the case shouldn't we be seeing OutOfMemory Errors somewhere? We have also backported fixes that were made in the StoreJanitor stuff in later Cocoon versions. Using TOP to check on the processes seems to indicate a growth in the number of Java threads - but this is may be caused by the incoming requests not being processed. So we are not sure whether this is the cause - or just a result of the hang. What we have found is that reducing the number of file handles will cause the hang to happen sooner. This however may be a separate thing and have nothing to do with the original problem. Of course if file handles are being leaked somewhere then we would still need to find out where that problem is coming from. We are using Sun JDK 1.3.1, Tomcat 3.3. Ok, so here are my questions to you Linux/Cocoon gurus out there: Have you seen anything like this happen - and if so what caused it? How many file handles do you have set on your Linux system? Do you have some pointers to the number we should have? We are also considering running the same application in Resin to see if this prompts at least some error message. What do you think? It really does seem as though the application is eating something up and then running out of whatever it is - but it is just not telling us :(. Sorry this is so long but I am hoping some of the information is setting off an alarm-bell or two out there. Any tips, ideas welcome. Thanks Matthew Langham -- Open Source Group sunShine - Lighting up e:Business ================================================================= Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de Weblogging at: http://www.need-a-cake.com ================================================================= --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
