Connection leak when database error occurs causes JIRA to eventually hang

Under certain conditions, connections are leaked:

• Tomcat (not certain if we need this)
• Oracle (with tryclob...) or MSSQL
• Try running quicksearch with a key that isn't found - this will search through the change history
• Because Oracle (and MSSQL presumably) can't do exact text match queries in CLOBs (though 'like' queries work), and exception is thrown
• This exception propagates up to JIRA code. However, ofbiz doesn't close the connection.
• If you do this enough times (more than number of connections in DB pool - 8 in Tomcat's commons-dbcp) then you run out of connections, and JIRA appears to hang.