[SERVER-19682] Prevent JSThread exceptions in concurrency suite when global db is undefined Created: 31/Jul/15 Updated: 08/Jan/24 Resolved: 31/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.1.6 |
| Fix Version/s: | 3.1.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kamran K. | Assignee: | Kamran K. |
| 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 | ||||||||
| Sprint: | Sharding 7 08/10/15 | ||||||||
| Participants: | |||||||||
| Description |
|
The concurrency suite will print out these JSThread exceptions when a global db variable is undefined:
This is because guardedThreadFn in fsm_libs/thread_mgr.js unconditionally assigns null to db to aid garbage collection. |
| Comments |
| Comment by Githook User [ 31/Jul/15 ] |
|
Author: {u'username': u'kkmongo', u'name': u'Kamran Khan', u'email': u'kamran.khan@mongodb.com'}Message: The global 'db' variable is undefined when the shell is run with --nodb, |