You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Yaytay (JIRA)" <ji...@apache.org> on 2012/08/20 12:10:37 UTC
[jira] [Created] (OPENJPA-2253) Memory leak in Audit feature
Yaytay created OPENJPA-2253:
-------------------------------
Summary: Memory leak in Audit feature
Key: OPENJPA-2253
URL: https://issues.apache.org/jira/browse/OPENJPA-2253
Project: OpenJPA
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Yaytay
Priority: Blocker
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:
http://mail-archives.apache.org/mod_mbox/openjpa-users/201208.mbox/browser
Quote: I think the problem is that in
AuditManager<eclipse-javadoc:%E2%98%82=openjpa-kernel/src%5C/main%5C/java%3Corg.apache.openjpa.kernel%7BAuditManager.java%E2%98%83AuditManager>.afterBegin(...)
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENJPA-2253) Memory leak in Audit feature
Posted by "Rick Curtis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis updated OPENJPA-2253:
---------------------------------
Fix Version/s: 2.3.0
> Memory leak in Audit feature
> ----------------------------
>
> Key: OPENJPA-2253
> URL: https://issues.apache.org/jira/browse/OPENJPA-2253
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.2.0, 2.3.0
> Reporter: Yaytay
> Assignee: Pinaki Poddar
> Priority: Blocker
> Fix For: 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:
> http://mail-archives.apache.org/mod_mbox/openjpa-users/201208.mbox/browser
> Quote: I think the problem is that in
> AuditManager<eclipse-javadoc:%E2%98%82=openjpa-kernel/src%5C/main%5C/java%3Corg.apache.openjpa.kernel%7BAuditManager.java%E2%98%83AuditManager>.afterBegin(...)
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENJPA-2253) Memory leak in Audit feature
Posted by "Rick Curtis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis updated OPENJPA-2253:
---------------------------------
Affects Version/s: 2.3.0
> Memory leak in Audit feature
> ----------------------------
>
> Key: OPENJPA-2253
> URL: https://issues.apache.org/jira/browse/OPENJPA-2253
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.2.0, 2.3.0
> Reporter: Yaytay
> Assignee: Pinaki Poddar
> Priority: Blocker
> Fix For: 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:
> http://mail-archives.apache.org/mod_mbox/openjpa-users/201208.mbox/browser
> Quote: I think the problem is that in
> AuditManager<eclipse-javadoc:%E2%98%82=openjpa-kernel/src%5C/main%5C/java%3Corg.apache.openjpa.kernel%7BAuditManager.java%E2%98%83AuditManager>.afterBegin(...)
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OPENJPA-2253) Memory leak in Audit feature
Posted by "Rick Curtis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis reassigned OPENJPA-2253:
------------------------------------
Assignee: Pinaki Poddar
Pinaki -- I see you committed some changes for this JIRA.
Yaytay -- Can you confirm that his changes fix your problem?
> Memory leak in Audit feature
> ----------------------------
>
> Key: OPENJPA-2253
> URL: https://issues.apache.org/jira/browse/OPENJPA-2253
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.2.0, 2.3.0
> Reporter: Yaytay
> Assignee: Pinaki Poddar
> Priority: Blocker
> Fix For: 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:
> http://mail-archives.apache.org/mod_mbox/openjpa-users/201208.mbox/browser
> Quote: I think the problem is that in
> AuditManager<eclipse-javadoc:%E2%98%82=openjpa-kernel/src%5C/main%5C/java%3Corg.apache.openjpa.kernel%7BAuditManager.java%E2%98%83AuditManager>.afterBegin(...)
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira