OK - I only noticed that it was marked as unresolved. I haven't tried the audit log feature in quite a while now (although I was part of initiating it some time back). I had class loading issues under OSGi but have found a workaround. But, because the report of memory leak I've postponed trying it out. I myself have never gotten so far as to notice a memory leak.
It would be good if Yaytay could verify your fix. I will probably start looking at the audit log again in a not to distant future but I don't have a test case myself. /Bengt 2012/10/9 Rick Curtis <[email protected]> > Bengt -- > > This change was committed to trunk, but no one has confirmed that it indeed > fixes the leak. > > Thanks, > RIck > > On Tue, Oct 9, 2012 at 1:56 PM, Bengt Rodehav <[email protected]> wrote: > > > I was really hoping to get the audit log feature working in this release. > > The feature has been around for quite a while but is not usable because > of > > memory leaks. Is it possible to get OPENJPA-2253 into this release? > > > > /Bengt > > > > 2012/10/9 Albert Lee <[email protected]> > > > > > We are planning to start releasing OpenJPA 2.2.1 shortly. > > > > > > If you have any concern, please post it here asap. > > > > > > -- > > > Albert Lee. > > > > > > > > > -- > *Rick Curtis* >
