Running out of memory for large operation with many native SQL queries because BulkOperationCleanupAction are not freed until transaction close ----------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-6220 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6220 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.3 Reporter: Dobes Vandermeer 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira