[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:
Duplicate
is duplicated by SERVER-12764 Using maxTimeMS & Javascript can lead... Closed
Related
related to SERVER-2212 Server automatically abort queries/co... Closed
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 SERVER-12764 for examples to reproduce.

Generated at Thu Feb 08 03:24:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.