-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: legacy-1.1.0
-
Component/s: API
This behaviour repeated when connection breaks (as example server was stopped) and then running has finished with segmentation fault.
Crutch-solution for client-code as I see, is check before by method isStillConnected(), but this method too is not absolutely good other bug
- related to
-
CXX-905 Strange results of DBClientConnection::isStillConnected()
- Closed