.
Best Regards,
Neale Rudd
metawerx
http://www.metawerx.net
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Thursday, 25 April 2002 3:21
Subject: Re: Servlet killing tracking
> My problem is not a deadlock. My p
> 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
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 destroyed? if it
>
> 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
;Tomcat Users List" <[EMAIL PROTECTED]>;
><[EMAIL PROTECTED]>
>Sent: Wednesday, April 24, 2002 7:14 PM
>Subject: RE: Servlet killing tracking
>
>> Hi,
>>
>> I don't have an answer for your deadlock?? Problem, but you might try
>> downloadi
...
Thanks for your help
- Original Message -
From: "Jay Gardner" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Wednesday, April 24, 2002 7:14 PM
Subject: RE: Servlet killing tracking
> Hi,
>
> I d
le 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 ki
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
