[SERVER-11730] Debugging output of connections with unexpected data Created: 15/Nov/13 Updated: 11/Jul/16 Resolved: 21/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Mark Benvenuto |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Sometimes our socket sanity checks detect sockets in the pool with remaining data - this should not happen, and may be due to incorrect pool management. Debugging this problem (only in debug mode) requires recv'ing/displaying this info when it exists and outputting the last operation sent over the socket. |
| Comments |
| Comment by Githook User [ 21/Jan/14 ] |
|
Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}Message: |
| Comment by Githook User [ 14/Jan/14 ] |
|
Author: {u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}Message: |