Project:
| View Revisions: Issue #20261 | [ Back to Issue ] | ||
| Summary | 0020261: SessionInfo PreparedStatement is not closed | ||
| Revision | 2012-04-13 09:44 by alostale | ||
| Description | When there is at least one table fully audited, on each request a temporary table (ad_context_info) is populated with context information. The PreparedStatement used for this population is never closed. This causes a memory leak in JVM as well as DB not releasing resources (open cursors in Oracle) making the application to degrade over time. See attached a screenshot of memory consumption just after GC having 6 concurrent sessions during ~10min with a session ping of 500ms to simulate long usage. Second screenshot is taken in the same conditions after applying the fix. Both are taken in an instance using Oracle. |
||
| Revision | 2012-04-13 09:40 by alostale | ||
| Description | When there is at least one table fully audited, on each request a temporary table (ad_context_info) is populated with context information. The PreparedStatement used for this population is never closed. This causes a memory leak in JVM as well as DB not releasing resources (open cursors in Oracle) making the application to degrade over time. See attached a screenshot of memory consumption just after GC having 6 concurrent sessions during ~10min with a session ping of 500ms to simulate long usage. Second screenshot is taken in the same conditions after applying the fix. |
||
| Revision | 2012-04-13 09:37 by alostale | ||
| Description | When there is at least one table fully audited, on each request a temporary table (ad_context_info) is populated with context information. The PreparedStatement used for this population is never closed. This causes a memory leak in JVM as well as DB not releasing resources (open cursors in Oracle) making the application to degrade over time. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |