[SERVER-5300] Connection identifiers don't match between accept and end connection Created: 13/Mar/12 Updated: 14/Mar/12 Resolved: 14/Mar/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.0.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Andrew Harbick | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Here's a sample from my log: Tue Mar 13 15:30:57 [initandlisten] connection accepted from 10.40.34.6:64663 #17859914 Tue Mar 13 15:31:24 [conn17859899] warning: newExtent 4646 scanned Tue Mar 13 15:31:24 [conn17859899] build index done 0 records 0.405 secs I logged in, created a collection with one record, dropped the collection, and then signed out. NOTE that the connection identifiers don't match: 17859914 != 17859899 I have other examples of this same pattern in our log as well... I do not know however whether it has always been this way (for example maybe they matched at some point, but after a while it drifted out of whack). |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 14/Mar/12 ] |
|
See |