Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 336409

Summary:	Refine error handling of exception caught at IQuery#close method
Product:	[Tools] Data Tools	Reporter:	Linda Chan <lchan>
Component:	Open Data Access	Assignee:	Linda Chan <lchan>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	lzhu
Version:	1.8.1
Target Milestone:	1.8.2
Hardware:	PC
OS:	All
Whiteboard:

Description Linda Chan

2011-02-04 21:38:26 EST

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.

Comment 1 Linda Chan

2011-02-04 22:13:27 EST

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.

Comment 2 Lin Zhu

2011-03-14 20:06:47 EDT

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.