If the component has a short lifetime then perhaps you could use a timer
thread (debugging only obviously) that starts screaming if a component
is not recycled/released in less than x seconds.

Corey

On Thu, 2002-08-01 at 17:11, Torsten Curdt wrote:
> On Thursday 01 August 2002 19:07, Berin Loritsch wrote:
> > > From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
> > >
> > > BTW, fillInStackTrace() is a native method (AKA a JNI method).
> >
> > oh yeah, it is synchronized as well.
> >
> > Creating tons of exceptions in a multithreaded environment is
> > not advised.
> 
> well, a boolean should do it (see example) and the Exception could be created 
> in finalize. Is there any other way a component could be aware of if it is 
> used or not?
> --
> Torsten
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> 



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to