-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Shell
-
None
-
Fully Compatible
-
ALL
Discovered whilst verifying SERVER-10747. Mathias requested that I assign this to him, he knows how to fix it.
1. Run a query which blocks other queries.
2. In a mongo shell, run a query.
3. Get "JavaScript execution terminated" message in the shell
4. Now try to run anything. Your shell is hosed.
Example: using blocker query found in SERVER-10747
Window A: issue blocker query
Window B:
$ mongo MongoDB shell version: 2.4.3 connecting to: test > db.cu<tab> (~60 sec passes) Mon Sep 16 13:40:18.711 JavaScript execution terminated db.cu<tab> Mon Sep 16 13:42:58.206 JavaScript execution terminated error2:JavaScript execution terminated > db.cuMon Sep 16 13:43:02.450 JavaScript execution terminated db.cu Mon Sep 16 13:43:21.818 JavaScript execution terminated error2:JavaScript execution terminated > db.currentOp(); Mon Sep 16 13:43:27.215 JavaScript execution terminated error2:JavaScript execution terminated
- duplicates
-
SERVER-9238 Shell stops working after long autocomplete operation
- Closed