On Wed, May 14, 2008 at 10:44 AM, Stuart McCulloch
<[EMAIL PROTECTED]> wrote:
> 2008/5/14 Roshan Punnoose <[EMAIL PROTECTED]>:
>
> >
> > I was profiling my osgi app and I noticed that pax logging doesn't release
> LogEntryImpl objects. The reason for this is that the LogReaderServiceImpl
> holds a
2008/5/14 Stuart McCulloch <[EMAIL PROTECTED]>:
> 2008/5/14 Roshan Punnoose <[EMAIL PROTECTED]>:
>
> > I was profiling my osgi app and I noticed that pax logging doesn't
> > release LogEntryImpl objects. The reason for this is that the
> > LogReaderServiceImpl holds a Vector of all LogEntries. Is
2008/5/14 Roshan Punnoose <[EMAIL PROTECTED]>:
> I was profiling my osgi app and I noticed that pax logging doesn't
> release LogEntryImpl objects. The reason for this is that the
> LogReaderServiceImpl holds a Vector of all LogEntries. Is this by design?
> There should be a cleanup of those entr
I was profiling my osgi app and I noticed that pax logging doesn¹t release
LogEntryImpl objects. The reason for this is that the LogReaderServiceImpl
holds a Vector of all LogEntries. Is this by design? There should be a
cleanup of those entries?
Roshan
