[SERVER-11094] Javascript interruption should use semantic "operation interrupted" error codes Created: 09/Oct/13 Updated: 14/Dec/17 Resolved: 14/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | 2.5.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | platforms-re-triaged | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Interrupting a Javascript operation currently sets the operation's error code to any of: 16711, 16712, 13475, 16721. Javascript interruption should use the same error codes that other server operations use on interruption (currently 11600/11601/50 for shutdown/killop/maxtime). This would allow drivers to more easily detect the type of failure mode and propagate the appropriate exception to the application. |
| Comments |
| Comment by J Rassi [ 23/Feb/14 ] |
|
See linked issue |