-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
https://github.com/ironjacamar/ironjacamar/pull/622, https://github.com/ironjacamar/ironjacamar/pull/621, https://github.com/ironjacamar/ironjacamar/pull/620, https://github.com/ironjacamar/ironjacamar/pull/613, https://github.com/ironjacamar/ironjacamar/pull/612, https://github.com/ironjacamar/ironjacamar/pull/611, https://github.com/ironjacamar/ironjacamar/pull/606, https://github.com/ironjacamar/ironjacamar/pull/607, https://github.com/ironjacamar/ironjacamar/pull/608
Various version of pre 11.x DB2 drivers utilize the -99999 error code for a SQLException. Not all -99999 errors are fatal. For those variations that are known to be fatal, a check should be added to treat as such.
One example would be the -99999 error that indicates "Connection is closed"
- is cloned by
-
JBEAP-9691 (7.1.0) Account for additional DB2 FATAL connection errors
- Closed