Hi, I don't have an answer for your deadlock?? Problem, but you might try downloading either Netbeans or Forte for Java. They have a debugger that works well for debugging servlets. They are both free and come with an integrated tomcat 3.2 container. With the debugger you may be able to 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, 2002 10:44 AM To: Tomcat Users List Subject: Re: Servlet killing tracking 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 generally. For instance, it does not respect > SingleThreadModel at all, and i've had other funkiness like you're > describing. > > I recommend you try a newer version of tomcat (as tomcat 4 is MUCH > higher throughput than 3). > > > > At Wednesday, 24 April 2002, you wrote: > > >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 killed my > >servlet ?! > > > >Thanks, > > > >Nicolas JACQUELINE > > > >-- > >To unsubscribe: <mailto:[EMAIL PROTECTED]> > >For additional commands: <mailto:[EMAIL PROTECTED]> > >Troubles with the list: <mailto:[EMAIL PROTECTED]> > > > > > > > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
