#1 - I have a reasonable command of commons logging, log4j, juli, java logging, etc., and I can quite easily make the application logging work without a hitch. As for 'production ready logging', I would look to valves for things like access logging. The access log valve works virtually the same as Apache httpd, or at least the output is nearly so. It didn't take me all that long to learn this stuff. I will admit I haven't used Tomcat virtual hosts, so that might be an area of concern.
#2 - Do any commercial application server vendors offer you assistance on how to find bugs in application code? You're much more likely to find these answers using google, or reading wikis or from community support. There are hundreds of such discussions out there. My favorite (personally) is how to avoid running out of permgen space. #3 really boils down to "The application developer screwed up so badly that the entire virtual machine under which Tomcat is running is toast." That's not Tomcat's fault, really, it's more Java's. Again, any commercially available server (written in Java/sharing the VM) will likely suffer the same fate. You can always feel free to contribute documentation improvements! Tim -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Tomasz Nowak Sent: Tuesday, February 28, 2006 4:36 PM To: users@tomcat.apache.org Subject: Re: Sad: Tomcat 5.5.x crashes almost every single day. Tim Lucia <[EMAIL PROTECTED]> wrote: > > Send Tomcat a QUIT (11) signal on Unix, or control/break (run it > interactively) on Windows. This will cause the VM to dump all thread > stacks. > > If you don't like Tomcat, you can always shell out some big bugs for a > commercial application server. For some even bigger bucks you can get > commercial support. I can tell you it's unlikely you'll get a warm > reception from the very people who can help you given the current tone > of your postings. Your right, the tone of my postings is inproper. I've been using 'free' software for almost 10 years now and I pretty well get the rules. My only excuse is the level of my frustration, based on recent Tomcat use. For now, the only contribition to Tomcat community I can give is _pointing_out_ some real-world problems, that typical users of Tomcat may face (and face!). The problems are: 1. Poor/none default logging facility in 5.5.x. - no real help/tips on error sources - no examples how to do a decent virtual hosts logging - no tips how to switch off a lot of uneccesary trash log inputs If Tomcat is supposed to be production ready why it has no production ready logging features? 2. No real-world, step-by-step docs how to TRACE and eliminate application errors that lead to server failure. That is probably a problem lot of Tomcat users must struggle with. 3. During last years I see no actions taken by Tomcat dev team to eliminate Tomcat server failures caused by webaplications. Is it really impossible? Real world user feedback was the main point of my postings. And sorry for the tone again. -- T. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
