[SERVER-7843] any V8 error during a query from the shell results in "new socket error on query" Created: 04/Dec/12 Updated: 11/Jul/16 Resolved: 25/Jan/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The v8 shell (and mongoFind) method catch and wrap all (...) exceptions as a "socket error on query message". In many cases, this is incorrect, and we should also bubble up the actual error message if possible with causedBy(). Also applies to all other mongoXXX operations. |
| Comments |
| Comment by auto [ 26/Jan/13 ] |
|
Author: {u'date': u'2013-01-26T15:25:34Z', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}Message: Use the toString() method of Error (and derived) objects to convert them |
| Comment by auto [ 25/Jan/13 ] |
|
Author: {u'date': u'2013-01-25T21:41:49Z', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}Message: Audit all handling of C++ and JavaScript exceptions in V8 interface code. |
| Comment by Tad Marshall [ 04/Dec/12 ] |
|
This may be a subset of |