[JAVA-1345] Handle asynchronously delivered exceptions in connection pool Created: 05/Aug/14  Updated: 31/Mar/15  Resolved: 10/Dec/14

Status: Closed
Project: Java Driver
Component/s: Async, Connection Management
Affects Version/s: None
Fix Version/s: 3.0.0

Type: Improvement Priority: Major - P3
Reporter: Jeffrey Yemin Assignee: Jeffrey Yemin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: Async

 Description   

DefaultConnectionPool catches and re-throws exceptions from the wrapped connection for synchronous calls, incrementing the generation count. But it does not for sendMessageAsync or receiveMessageAsync.



 Comments   
Comment by Jeffrey Yemin [ 31/Mar/15 ]

Closing all resolved 3.0.0 issues, as 3.0.0 has been tagged and released.

Comment by Githook User [ 30/Jan/15 ]

Author:

{u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}

Message: Connection pool invalidated when an asynchronous socket exception is returned from send or receive message callbacks.

JAVA-1345
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/f97a622850d2d311bf7935eec2394817a533a75a

Comment by Githook User [ 10/Dec/14 ]

Author:

{u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}

Message: Connection pool invalidated when an asynchronous socket exception is returned from send or receive message callbacks.

JAVA-1345
Branch: 3.0.x
https://github.com/mongodb/mongo-java-driver/commit/f97a622850d2d311bf7935eec2394817a533a75a

Generated at Thu Feb 08 08:54:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.