> fair enough. some response questions in light of the new information
you've
> provided:
>
> 1) what exactly does your servlet depend on in int() and destroy() that is
> so vital?
> 2) i asked this before but it probably wasn't clear: does Tomcat never
> re-init the servlet once it's been des
>
> i sent you one email already, but i will tell you this again, i have
> experienced many oddities in the servlet lifecycle with tomcat 3.
> 2.x. I strongly suggest you try (at least in a test environment)
> 3.3 or 4.x as in my experience these are much cleaner WRT the life
> cycle problems you
> validate whether you have an application deadlock.
>
> http://www.netbeans.org
>
> Best of luck,
>
> --Jay Gardner
>
> -Original Message-
> From: JACQUELINE Nicolas - REN ( [EMAIL PROTECTED] )
> [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 24
I'm not using SingleThreadModel, and as I'm using Tomcat in a professional
context, I cant upgrade to a newer version. That's why I need to track what
makes Tomcat destroy my servlet.
Any idea ?
>
> it has been my experience that tomcat 3.2.x is pretty poor at managing
> the servlet lifecycle g
Hi everybody,
I'm using Tomcat 3.2.3 on a linux system to run a servlet-based service.
This application must support a high number of connected people (about
1000).
The service works fine, but sometimes Tomcat kills my servlet (calls
Servlet.destroy) for no reason. How could I track why Tomcat k
