John C. Dale <[EMAIL PROTECTED]> wrote: > > Don't give-up on Tomcat so soon.
At least 3 years of giving a chance are not "soon"... ;] > Sometimes Tomcat is only as good as the applications deployed within > her. "Operating system is only as good as the applications run on it." True of false? True... in Windows 95 :-) Few years later even Microsoft handles apps erros successfully. Tomcat is the only server-type software I know that _any_user_ can crash so easily and the only that is so helpless about handling their erros. Why don't it send 500 status to pages in faulty webapp and contiunes to serve other webapps normally? > I write my own apps ;o) I use Apache Foundation apps ;] > I would stick with it, and cease development of new code until you > have eliminated the existing installed code I'm so sad that I think of a _completly_ new code. In PHP! > Along the way, it would > be helpful for you to beat up a separate, mirrored staging instance > of your production environment using JMeter. Reproduce your problem > with regularity by hitting each URL many times, then examining the > results. This is probably imposibble because: - the apps have _plenty_ of different urls. - I can't reproduce such Tomcat hangs on development machine. - Shall I really examin and monitor the production enviroment? What about performance then? Are there any resource monitors built-in into Tomcat? I've browsed the JMX management manual.. well is it written for a human being? Looks like a "finish it yourself" thing. :| -- Tomasz Nowak Netventure, http://www.netventure.pl/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
