[JAVA-4321] CommandFailedEvent (and debug log) is generated if decoding fails Created: 29/Sep/21 Updated: 28/Oct/23 Resolved: 04/Oct/21 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Monitoring |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Expected outcome: For each command sent to the server, the driver should generate either a CommandSucceededEvent or a CommandFailedEvent. Actual outcome: The driver generates both CommandSucceededEvent and CommandFailedEvent. This can will happen in any situation where the registered Decoder for the response throws an exception decoding the BSON document response.
|
| Comments |
| Comment by Githook User [ 04/Oct/21 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Fixed new tests on 4.3.x branch
|
| Comment by Githook User [ 04/Oct/21 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Either CommandFailed or CommandSucceeded event should be published, not both (#793) This fixes a bug in the synchronous driver in which the driver sends a CommandSucceededEvent,
|
| Comment by Githook User [ 04/Oct/21 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Either CommandFailed or CommandSucceeded event should be published, not both (#793) This fixes a bug in the synchronous driver in which the driver sends a CommandSucceededEvent,
|