| Bug #71850 | init() is called twice on exception interceptors | ||
|---|---|---|---|
| Submitted: | 26 Feb 2014 22:59 | Modified: | 3 Apr 2014 16:00 |
| Reporter: | Jess Balint | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / J | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | Alexander Soklakov | CPU Architecture: | Any |
| Tags: | interceptor | ||
[3 Apr 2014 16:00]
Daniel So
Added the following entry into the Connector/J 5.1.31 changelog: "When exception interceptors were used, the init() method was called twice for each exception interceptor, once by Util.loadExtensions() and again by ConnectionImpl.ExceptionInterceptorChain.init(). This fix eliminates the calls by ExceptionInterceptorChain.init()."

Description: The init() method of exception interceptors is called once by: Util.loadExtensions() and a second time by: ConnectionImpl.ExceptionInterceptorChain.init() How to repeat: create a connection with an exception interceptor and it will be called twice Suggested fix: don't call init() for each interceptor in ExceptionInterceptorChain.init()