[SERVER-2696] Socket Error: accept() returns -1 errno:10038 Created: 07/Mar/11 Updated: 08/Mar/13 Resolved: 10/Oct/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 1.8.0-rc1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | Windows |
| Participants: |
| Description |
|
Running with --dur on windows x64 Sun Mar 06 23:55:02 [dur] lsn set 419075 |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 22/Sep/12 ] |
|
Max, are you still seeing this on newer releases of the server? |
| Comment by Scott Hernandez (Inactive) [ 23/Jul/12 ] |
|
What is the exception in the client logs? Can you post the full mongodb logs please? |
| Comment by Max Mumford [ 23/Jul/12 ] |
|
I am still experiencing this problem using the C# driver to access a mongodb running version 2.0.6. When accessing the server using: public Member GetMemberById(string memberID) { IMongoQuery query = Query.EQ("_id", memberID); return (Member) memberCollection.FindOneAs(typeof(Member), query); }The method succeeds 9 out of 10 times but fails with the exception mentioned in this original bug report. Is there any information on workarounds or fixes for this issue? |