honestly, I really doubt logging will produce anything useful beyond the VM dump you already posted. My first hand experience, the logs won't help at this point. What needs to happen is to step through the code and see exactly what is happening.
if you don't have access to a profiler, the other option is to add a bunch of system.out.println to the pages to see what is happening. If the webapp is making connection to a database or anything external, I would double check that code. Chances are, the code is leaking badly and causing the instability. peter On 3/1/06, Tomasz Nowak <[EMAIL PROTECTED]> wrote: > > Peter Lin <[EMAIL PROTECTED]> wrote: > > > > my advice is dive in and try to debug it, or hire someone with > > experience debugging webapps. > > > > there's no much others can do for you at this point, since it's > > debugging. good luck. > > I've just meant configuring the logging system: > > > > > So how can I: > > > > - configure it to work similary to tomcat 4.1, I mean > > > > logs from different vhost go to different files > > > > - configure Tomcat not to log anything that belongs to vhost > > > > to catalina.out > > > > - turn of these useless jk infos > > > > > > Any help on above would be _really_ appreciated! > > Tomcat 5.5 logging docs are very brief about it.. > Simple duplication of example entries does not do the job. > > -- > T. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
