[SERVER-15923] DeadLockException is incorrectly and severely misleadingly named Created: 03/Nov/14 Updated: 11/Jul/16 Resolved: 03/Nov/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
DeadLockException is actually only thrown for write conflicts. It is more aptly named WriteConflictException. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 03/Nov/14 ] |
|
https://github.com/mongodb/mongo/commit/aa67a4e69eeb73fedc64f9a9588c2fa24cf8c6ab |
| Comment by Eliot Horowitz (Inactive) [ 03/Nov/14 ] |
|
Going with WriteConflictException |