[CXX-328] MCI locking error in unittests Created: 03/Sep/14  Updated: 23/Oct/14  Resolved: 26/Sep/14

Status: Closed
Project: C++ Driver
Component/s: Testing
Affects Version/s: None
Fix Version/s: legacy-1.0.0-rc1

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

Issue Links:
Related
related to SERVER-15361 BackgroundJob should not access the S... Closed

 Description   

Errors in our unit tests in MCI, looks to be some sort of locking problem:

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::lock_error> >'

and

[2014/09/03 15:19:30.056] what(): boost: mutex lock failed in pthread_mutex_lock: Invalid argument



 Comments   
Comment by Githook User [ 23/Sep/14 ]

Author:

{u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}

Message: CXX-318 Restore tests on windows now that CXX-328 is belived fixed
Branch: legacy
https://github.com/mongodb/mongo-cxx-driver/commit/470708dca0c014f45343b3d125cdda4c377b8fb7

Comment by Githook User [ 23/Sep/14 ]

Author:

{u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}

Message: CXX-328 Don't access SSLManager after notifying

See SERVER-15361 for additional details on this change
Branch: legacy
https://github.com/mongodb/mongo-cxx-driver/commit/7c40809ac93873f1d8b5714f30ff2067af6d11ce

Comment by Andrew Morrow (Inactive) [ 23/Sep/14 ]

Yes, see SERVER-15361 for details.

Comment by Adam Midvidy [ 23/Sep/14 ]

I think acm has a fix for this on the Server that should come by way of backport.

Comment by Andrew Morrow (Inactive) [ 06/Sep/14 ]

Have a look at CXX-247. We have seen this before.

Comment by Tyler Brock [ 04/Sep/14 ]

I don't see that commit as related to the mutex issue. I think MCI is leading us astray there.

Generated at Wed Feb 07 21:58:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.