title: MongoTransactionException: Query failed with error code 251
body: <p>Faced this Mongo exception when query a document in a transaction, with a <strong>specific id</strong> only (all other ids are fine):</p>
  <pre><code>Exception occured: org.springframework.data.mongodb.MongoTransactionException: 
  Query failed with error code 251 and error message 
  'Given transaction number 1 does not match any in-progress transactions. The active transaction number is -1' on server mongo-1:27017; 
  nested exception is com.mongodb.MongoQueryException: 
  Query failed with error code 251 and error message 
  'Given transaction number 1 does not match any in-progress transactions. The active transaction number is -1' on server mongo-1:27017 
  at org.springframework.data.mongodb.core.MongoExceptionTranslator.translateExceptionIfPossible(MongoExceptionTranslator.java:136) 
  at org.springframework.data.mongodb.core.MongoTemplate.potentiallyConvertRuntimeException(MongoTemplate.java:2902) 
  at org.springframework.data.mongodb.core.MongoTemplate.executeFindMultiInternal(MongoTemplate.java:2810) 
  at org.springframework.data.mongodb.core.MongoTemplate.doFind(MongoTemplate.java:2555) 
  at org.springframework.data.mongodb.core.ExecutableFindOperationSupport$ExecutableFindSupport.doFind(ExecutableFindOperationSupport.java:216) 
  at org.springframework.data.mongodb.core.ExecutableFindOperationSupport$ExecutableFindSupport.oneValue(ExecutableFindOperationSupport.java:128) 
  at org.springframework.data.mongodb.repository.query.AbstractMongoQuery.lambda$getExecution$4(AbstractMongoQuery.java:153) 
  at org.springframework.data.mongodb.repository.query.AbstractMongoQuery.doExecute(AbstractMongoQuery.java:126) 
  at org.springframework.data.mongodb.repository.query.AbstractMongoQuery.execute(AbstractMongoQuery.java:101) 
  at org.springframework.data.repository.core.support.RepositoryFactorySupport$QueryExecutorMethodInterceptor.doInvoke(RepositoryFactorySupport.java:618) 
  </code></pre>
  <p>The MongoDB is a sharded cluster, and similar action is performed against a completely similar cluster (in another test environment) but no exception occurs.</p>
  <p>Another info, this exception is always after a MongoDB socket exception as below:</p>
  <pre><code>Got socket exception on connection [connectionId{localValue:9, serverValue:11760}] to mongo-1:27017. All connections to mongo-1:27017 will be closed.
  </code></pre>