Sounds premature to blame Tomcat (or that version) for this. I can think of a lot of questions I would want to have answered before I assumed it was a problem specific to 3.3:
- does this happen when you run against Tomcat standalone, or only when running through Apache? mod_jk can be a pain in the &^%&^%, but in my experience it has always either completely worked or completely not worked. - what do you mean by "can't keep app running". Does the JVM exit? If not, what's the behavior? Error responses? Hung responses? - if responses are hanging, I would get a thread dump and expect to see one or more threads deadlocked. - does it happen in a single-client test, or only when multiple clients are accessing (again, that would indicate a threading problem) - is this something that worked satisfactorily with earlier versions of infrastructure and is only now breaking? Or is this new development? dwh Ed Tybursky wrote: > I am having major downtime issues currently our environment is this: > > Apache 1.3.20 + mod_jk > Tomcat 3.3 > > I cant seem to keep an application running for any matter of time. Nothing is ever >reflected in the logs and logging is set to DEBUG. Is tomcat 3.3 just a total piece >of junk?? should I at least upgrade to 3.3.1 or just totally move to 4.0?? > > I really need some help. > > Thanks > Ed -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
