[SERVER-2738] Better logging of socket exceptions in DBConnection Created: 11/Mar/11 Updated: 24/Feb/17 Resolved: 24/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Client |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Jared Rosoff | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 1 |
| Labels: | cxxcopy | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
In client/dbclient.cpp line 943, when a connection is established, we catch the error message in a temp variable and throw it away. Should log this error if present. In general, any exception thrown regarding connection processing should be logged. |
| Comments |
| Comment by Eric Milkie [ 24/Feb/17 ] |
|
The legacy C++ driver has been deprecated; the new C++ driver does not suffer from this issue. |
| Comment by Eliot Horowitz (Inactive) [ 18/Sep/12 ] |
|
This has changed a lot - so should treat this at general c++ error message cleanup/audit. |