[SERVER-26086] Invariant failure !conn->second.inUse in TransportLayerLegacy Created: 13/Sep/16  Updated: 19/Nov/16  Resolved: 13/Sep/16

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: 3.3.14
Fix Version/s: 3.3.14

Type: Bug Priority: Blocker - P1
Reporter: Samantha Ritter (Inactive) Assignee: Samantha Ritter (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Platforms 2016-09-19
Participants:
Linked BF Score: 0

 Description   

We assumed that a connection that was being _destroy()ed could not also be inUse. I triggered this invariant by starting a mongod with ssl required and attempting to connect to it without using ssl:

> ./mongod --dbpath=data/db --sslMode requireSSL --sslPEMKeyFile /etc/ssl/mongodb.pem

>./mongo

 mongod(_ZN5mongo15printStackTraceERSo+0x23) [0x7fd459fd35a3]
 mongod(+0x2A0E1B5) [0x7fd459fd31b5]
 mongod(+0x2A0DB4C) [0x7fd459fd2b4c]
 libpthread.so.0(+0x10340) [0x7fd454633340]
 libc.so.6(gsignal+0x39) [0x7fd454293cc9]
 libc.so.6(abort+0x148) [0x7fd4542970d8]
 mongod(_ZN5mongo15invariantFailedEPKcS1_j+0x17E) [0x7fd459f0ac0e]
 mongod(_ZN5mongo9transport20TransportLayerLegacy8_destroyERNS0_7SessionE+0x165) [0x7fd459f00aa5]
 mongod(_ZN5mongo9transport7SessionD2Ev+0x36) [0x7fd459efdad6]
 mongod(+0x293851C) [0x7fd459efd51c]
 mongod(+0x293840B) [0x7fd459efd40b]
 mongod(+0x2938103) [0x7fd459efd103]
 mongod(+0x2937F55) [0x7fd459efcf55]
 libpthread.so.0(+0x8182) [0x7fd45462b182]
 libc.so.6(clone+0x6D) [0x7fd45435800d]



 Comments   
Comment by Githook User [ 13/Sep/16 ]

Author:

{u'username': u'samantharitter', u'name': u'samantharitter', u'email': u'samantha.ritter@10gen.com'}

Message: SERVER-26086 Handle exceptions that occur while running TransportLayer tickets
Branch: master
https://github.com/mongodb/mongo/commit/23640a0987b531c01d012a0644a87f9be8895716

Generated at Thu Feb 08 04:11:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.