SERVER-4328 use a mutex of its own for OpTime::now. we stay in the mutex for a while after grabbing an optime so that we dont have to reason too much about different threads grabbing optimes and then using them out of order.

1 files changed, 2 insertions, 2 deletions

diff --git a/src/mongo/dbtests/jsobjtests.cpp b/src/mongo/dbtests/jsobjtests.cpp
index 586a11745ab..47171b7c993 100644
--- a/src/mongo/dbtests/jsobjtests.cpp
+++ b/src/mongo/dbtests/jsobjtests.cpp
@@ -314,9 +314,9 @@ namespace JsobjTests {
                 e = i.next();
                 ASSERT( e.eoo() );
 
-                OpTime before = OpTime::now();
+                OpTime before = OpTime::_now();
                 BSONElementManipulator( o.firstElement() ).initTimestamp();
-                OpTime after = OpTime::now();
+                OpTime after = OpTime::_now();
 
                 OpTime test = OpTime( o.firstElement().date() );
                 ASSERT( before < test && test < after );