John C. Dale <[EMAIL PROTECTED]> wrote: > > PHP is great. So is Zoap and .NET. Careful, though, some of the same > problems you would be shunning Java for would also appear in any > Internet development/application development platform.
I know the pitfalls of PHP, I been developing php webapps before. That's why I moved to Java ;) But as far as I remember: - I've never managed to hang httpd with a buggy PHP script :) - I could _easly_ diagnose ANY PHP bug just by browsing the log file. I'd love Tomcat behave similar. > There is a correlation between the size of the application and the > time it takes to properly test the application. The larger the > application, the more it takes to vet application quality. What you > have said here is that you don't want to properly test the > application because it's too large and too much work, and that you > are happy to continually restart the application as a solution. > Sounds equitable. You seems reasonable, but souldn't the appserver at least try to help me a bit? I'd really like to see something more than "An error occurred. I quitting. Bye!" An error where? Which vhost? Which webapp? Which class? Anything, please. > And with regularity, what steps lead up to Tomcat hanging? This is > the question that you should try to answer with increasing accuracy > each time Tomcat hangs until you find the issue. Once you do, submit > it as a bug, and give back to the OS community that has been > supporting your applications for 3 years. No hangs regularity. Nothing special in the log files. No starting point out of the box. Please, browse the mailinig list topics. I'm not the only one here with such problems. Different people post similar stories. Are we all wrong? -- T. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
