On Thursday 01 August 2002 01:06 pm, Berin Loritsch wrote: > I take that back. I checked the source code for Throwable, it > does fill in the stack trace on creation. > > Exceptions cause a strain on the JVM in all respects. Both creation > and throwing. > > Keep in mind that if you "precreate" your exception to throw later, > you incurr the fillInStackTrace() call twice. You have to call it > again later to make sure it makes sense.
The idea is to "precreate" the exception when the component is looked up, because you have then captured the line of code that is doing the lookup w/o the matching release. To answer Corey, yes this should be a debugging-only option for when you think you may have a leak in your pool. Maybe this should be the excalibur/caulk project :) -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
