[JAVA-3857] “The responseTo (1113396) in the response does not match the requestId (1113399) in the request” Created: 07/Oct/20 Updated: 27/Oct/23 Resolved: 27/Oct/20 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Wire Protocol |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Firass Almiski | Assignee: | Jeffrey Yemin |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
“The responseTo (1113396) in the response does not match the requestId (1113399) in the request” Occasionally seeing this returned from the java mongo client ‘org.mongodb:mongodb-driver-async:3.12.3’ – mainly during read requests. We have a sharded cluster with 20+ shards and 2 router nodes running mongodb community edition 4.4 on ARM64 machines in AWS. Anyone know more about this error, why it happens, how to resolve it – is this a bug? |
| Comments |
| Comment by Jeffrey Yemin [ 27/Oct/20 ] |
|
Hi falmiski@creativeradicals.com As we haven't heard back from you, we're closing this issue. If you can provide more information we'd be happy to re-open it. |
| Comment by Jeffrey Yemin [ 13/Oct/20 ] |
|
falmiski@creativeradicals.com thanks for reporting this issue. It sounds like a bug, but not one we've seen before. To progress our investigation, can you provide
Thanks, |
| Comment by Firass Almiski [ 12/Oct/20 ] |
|
I inquired about the compatibility with 4.4 on your community forums, where I was told it was. What triggers this error? It is very disturbing to our system. Is there a workaround? |
| Comment by Dmitry Agranat [ 11/Oct/20 ] |
|
Hi falmiski@creativeradicals.com, I've noticed you are using an incompatible Java driver with MongoDB 4.4. The first thing I recommend is adjusting your driver/server compatibility according to our documentation. As for the message itself, in the the Java driver we ensure the validity of the message header values. In particular we ensure the responseTo header in a reply from the server matches the original requestID header. Thanks, |