Possible connection leak in OracleManager

Metadata query methods in OracleManager use discardConnection(false) which sets this.connection to null, but does not call connection.close(). This will leave the connection open in the background until the server decides to dispose of it. here is a comment from Aaron on another thread:

For ditching the Connection object, you should call discardConnection(true) so it's closed. (The boolean parameter is there to allow the OracleManager.ConnCache to keep the connection object object but dispose of the reference.) You should actually probably just call OracleManager.close() which will recycle the Connection instance into the cache, for use by subsequent getConnection() calls.