Bug #49607 Provide Connection visibility to ExceptionInterceptor
Submitted: 10 Dec 2009 22:58 Modified: 18 Dec 2009 17:22
Reporter: Todd Farmer (OCA) Email Updates:
Status: Closed Impact on me:
Category:Connector / J Severity:S4 (Feature request)
Version:5.1.10 OS:Any
Assigned to: Todd Farmer CPU Architecture:Any

[10 Dec 2009 22:58] Todd Farmer
Having access to the Connection object in the ExceptionInterceptor is much-needed.  A use case where this is most needed is with Cluster, where mysqld will return an error, yet there will be further NDB-specific error codes and messages available if the SHOW ERRORS command is executed immediately afterwords.

How to repeat:

Suggested fix:
Provide Connection as an argument to the ExceptionInterceptor.interceptException() method.
[10 Dec 2009 23:01] Todd Farmer

Attachment: diff.txt (text/plain), 6.06 KiB.

[10 Dec 2009 23:02] Todd Farmer
Pushed in r882.
[18 Dec 2009 17:22] Tony Bedford
An entry has been added to the 5.2.11 changelog:

The ExceptionInterceptor class did not provide a Connection context.