Rejected
Details
Assignee
UnassignedUnassignedReporter
Dobes VandermeerDobes VandermeerAffects versions
Priority
Major
Details
Details
Assignee
Unassigned
UnassignedReporter
Dobes Vandermeer
Dobes VandermeerAffects versions
Priority
Created May 13, 2011 at 1:41 AM
Updated March 19, 2014 at 5:55 PM
Resolved October 30, 2013 at 9:27 AM
When running a long job which performs many SQL queries I eventually run out of memory.
This happens because the NativeSQLQueryPlan appends an action to the post-transaction action queue for each native SQL query that I run, and these cleanup operations seem to use a decent amount of memory.
There is no clear means by which these objects can be cleaned up besides closing and re-initiating a database transaction. This makes large database transactions that use native SQL queries impossible to write, without splitting them up (which in our case is not desirable).
The other workaround is to use JDBC directly.