MongoInternalException

JavaMongoExceptiongeneral

An exception indicating an internal driver error that should not normally occur

Related Jira Issues

JAVA-6358Closed
Netty transport: write on a server-closed connection with timeoutMS set throws non-retryable MongoInternalException (NoSuchElementException in addWriteTimeoutHandler)
h3. Summary With {{timeoutMS}} set and the Netty transport, a write on a pooled connection that the far side closed while idle fails with a non\-retryable {{MongoInternalException}} instead of a retryable {{MongoSocketException}}. Reported in HELP\-102596 \(reactive\-streams 5.6.5\). Reproduced on 5.6.5 and 5.14.0; {{NettyStream}} is unchanged on {{main}}. h3. Cause - Server closes an idle pooled connection. Netty's {{DefaultChannelPipeline}} destroys the pipeline on unregister. -
JAVA-6210Closed
Close connection on responseTo mismatch and harden async error handling to prevent stream desynchronization
Two categories of issue were identified in {{InternalStreamConnection}}: *1. No connection close on responseTo mismatch detection* {{getCommandResult()}} detects the mismatch and throws {{MongoInternalException}}, but callers in both the sync ({{sendAndReceive}}) and async ({{sendCommandMessageAsync}}) paths did not catch {{MongoInternalException}} separately — it fell through to the generic {{Exception}} handler which does *not* close the connection. The corrupted connection was re
JAVA-4122Closed
Getting Exceptions when CPU starving the driver
Using the Scala driver (4.2.3) when we switched over to the use of an Atlas cluster we started noticing some instabilities in our application.  We where for instance getting {code:java} com.mongodb.MongoInternalException: Unexpected runtime exception at com.mongodb.internal.connection.InternalStreamConnection.translateReadException(InternalStreamConnection.java:638) at com.mongodb.internal.connection.InternalStreamConnection.readAsync(InternalStreamConnection.java:591) at com.mongodb