I don't think that a debugger will help much in this case. A profiler might help, if you can reproduce the error in a test environment. (see below)
Some ideas: - Use the access log to try to reproduce the error in a test environment. (AFAIK apache jmeter has the ability to create a test case from an access log) If you can reproduce the error, try to cut down the test case to the bare minimum that exposes the problem, then you might have luck with a profiler. - Write a servlet filter that logs the processing time for each request. - Extend the filter to interrupt the current thread if it takes to long and dump some data. > -----Original Message----- > From: rlipi [mailto:[EMAIL PROTECTED] > Sent: Friday, May 07, 2004 2:20 PM > To: 'Tomcat Users List' > Subject: RE: How to limit time for Connector threads? > > Maybe I have wrong idea about possibilities of debugging tools but I > think that it will not help. We have above 100 000 hits a day and the > problem occurs only once a day. It can be a result of one special > request or (with greater probability) it is result of some combination > of requests. In both cases I don't know these requests nor the > particular place where the problem is. Therefore, I need some > statistical information about server behavior before problem > and/or all > possible information about server status in the time of problem. Can > debugger help me with this? > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
