[SERVER-64804] Log socket errors after a call to asio::set_option fails Created: 22/Mar/22 Updated: 29/Mar/22 Resolved: 29/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Morilha (Inactive) | Assignee: | Daniel Morilha (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Sprint: | Service Arch 2022-04-04 | ||||
| Participants: | |||||
| Linked BF Score: | 64 | ||||
| Description |
|
BF-24678 reported an unhandled exception on a socket connect due to asio::socket::set_option invalid parameter happening on Darwin. Despite the lack of exception handling later address by AC: This ticket is to augment setSocketOption logging and report the last socket error (if any) after setting options on it. |
| Comments |
| Comment by Daniel Morilha (Inactive) [ 29/Mar/22 ] |
|
We ended up deciding to not pursue this ticket. |