-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
As discussed in EAPSUP-671 some driver implementation may decide to close the underlying connections on endRequest notification leading to problems described in WFLY-15493. Altough, our suggestion was to don't use IronJacamar's prepared statement cache with such drivers, we may also clear the cache on endRequest notification to make sure that even in such configuration failure won't occurr.
- blocks
-
WFLY-15493 SQL Server Prepared Statements Cache no longer working on WF24 - WF25
- Open
- causes
-
JBJCA-1501 prepared statement cache flush on endRequest notification can degrade performance
- Closed
-
JBEAP-28152 [GSS](7.4.z) JBJCA-1504 - BaseWrapperManagedConnection: flush only closed connection on endRequest notification
- Open
-
JBEAP-28153 [GSS](8.0.z) JBJCA-1504 - BaseWrapperManagedConnection: flush only closed connection on endRequest notification
- Open