Community
Participate
Working Groups
When calling an ODA driver's implementation of IQuery#close method, if the ODA driver throws an exception, the ODA consumer framework currently handles it as a severe error. However, an error at #close may be safely ignored by a consumer application depending on the driver-specific implementation. It would be more robust to refine the error handling to proceed and handle such case as a warning instead.
As a consumer application may ignore the exception thrown by IQuery#close method implementation, the odaconsumer framework now handles it as a warning. In addition, an UnsupportedOperationException caught by the odaconsumer framework is now logged at the Warning level, instead of Severe level.
Add new configuration setting so that we can now tailor the JDBC driver to suppress not important SQL exceptions, say, the exception thrown during the close of a Statement/Connection.
