Affects Version/s: 2.2.0, 2.3.0
Fix Version/s: 2.3.0
Note: Is a blocker for the audit facility, removing audit lets us continue (obviously without any audit
We are getting major memory leaks from an OSGi application using OpenJPA with auditing (and with a custom auditor).
Mail thread with problem identified by Rick Curtis:
Quote: I think the problem is that in
we register a listener (Broker.addLifecycleListener), but we fail to
deregister this listener.
I've stopped auditing my large objects but the problem persists: any @Auditable object accessed remains in memory forever.