---------------------------------------------------------------- BEFORE YOU POST, search the faq at <http://java.apache.org/faq/> WHEN YOU POST, include all relevant version numbers, log files, and configuration files. Don't make us guess your problem!!! ---------------------------------------------------------------- I would suggest you use a profiler on a dos box, to track what the servlet is doing after the 12 hours is up. We had the same problem with http://www.musicdispatch.com, which uses extensive servlet technology along with Oracle on the Linux Platform. We used OptimizeIT to track a memory leak which would wack the jvm on the side of the head because it had memory leaks in the thread pooling manager one of my guys wrote. We used Jmeter to wack it for 5 days. Part of the deployment process is to use this and other techniques before we deploy the servlet. After 1.5 million requests we gave up trying to break it. :-) -gc -- -------------------------------------------------------------- Please read the FAQ! <http://java.apache.org/faq/> To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html> Problems?: [EMAIL PROTECTED]
