I'll tried to do so. 2010/8/20 Scott Ferguson <f...@caucho.com>: > Wesley Wu wrote: >> 2010/8/20 Scott Ferguson <f...@caucho.com>: >> >>> I still think there's a chance for a Resin leak; I just don't understand >>> where it's coming from. >>> >> >> I think so. The same code worked fine (no leak) in Resin 4.0.5. >> > > Do you have access to the eclipse "mat" program or some other heap > analyzer? > > If you can reproduce the issue, ask Resin to dump the heap (it's in > /resin-admin/memory with the jvm heap dump button), and then ask the > heap analyzer to trace the leaking memory to root, it would help track > down this issue greatly. > > -- Scott >> >>> It shouldn't matter what context you're injecting from, as long as >>> you're creating a new top-level CreationalContext. The getReference for >>> a dependent bean shouldn't have any references to it. >>> >>> -- Scott >>> >> >> >> _______________________________________________ >> resin-interest mailing list >> resin-interest@caucho.com >> http://maillist.caucho.com/mailman/listinfo/resin-interest >> >> > > > > _______________________________________________ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest >
_______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
