ThreadWithAttributes extends Thread and caches some info ( Request object for example ). Since they are threads - they don't need to be referenced, and won't get GC until the thread is done.
It's strange that it'll directly reference your classes. Costin On 3/7/06, Tino Schwarze <[EMAIL PROTECTED]> wrote: > Hi there, > > I'm currently tracking an OutOfMemory problem. We've got a web app which > gets OutOfMemory after some heavy use. I installed Mustang 1.6b62 on the > machines and had them dump heap on OOM. Then I looked into the heap dump > using jhat. > > I noticed that there are several objects hanging around with a strange > reference: > > Java Local Reference (from [EMAIL PROTECTED]) : > --> some.of.our.classes > > According to jhat, no other objects are referencing these objects (only > Finalizer). > > Has anybody a clue what might cause this? After all, they don't seem to > get garbage collected. > > Bye+Thanks! > > Tino. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
