[JAVA-1934] Netty readTimeout doesn't work as expected Created: 25/Aug/15  Updated: 14/Sep/15  Resolved: 09/Sep/15

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

Type: Bug Priority: Major - P3
Reporter: Ross Lawley Assignee: Ross Lawley
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to JAVA-1931 com.mongodb.MongoSocketWriteException... Closed

 Description   

Currently, NettyStream uses the readTimeout for the ReadTimeoutHandler.

The ReadTimeoutHandler closes the channel when there is no inbound traffic after the time, regardless of whether or not a read has been requested.

Currently, its more akin to MaxIdleTime than a read timeout.



 Comments   
Comment by Jeffrey Yemin [ 14/Sep/15 ]

Fix release today in 3.0.4.

Comment by Githook User [ 09/Sep/15 ]

Author:

{u'username': u'rozza', u'name': u'Ross Lawley', u'email': u'ross.lawley@gmail.com'}

Message: Only schedule a timeout if one doesn't already exist

JAVA-1934
Branch: 3.0.x
https://github.com/mongodb/mongo-java-driver/commit/0a6bbfcd9558f55115cca4e0ba02d7270864da77

Comment by Githook User [ 09/Sep/15 ]

Author:

{u'username': u'rozza', u'name': u'Ross Lawley', u'email': u'ross.lawley@gmail.com'}

Message: Only schedule a timeout if one doesn't already exist

JAVA-1934
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/e5d90268f837038b2b9bee3e290899610954d194

Comment by Ross Lawley [ 08/Sep/15 ]

Currently the timeout can be rescheduled and eventually will lead to a failure case.

Comment by Githook User [ 04/Sep/15 ]

Author:

{u'username': u'rozza', u'name': u'Ross Lawley', u'email': u'ross.lawley@gmail.com'}

Message: Fix Async Streams timeout behaviour

AsynchronousSocketChannelStream no longer wraps open or timeout exceptions
Netty now respects the read timeout setting correctly.

JAVA-1934
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/a50c92f6fa17d9214225ed0076b3dd387367ff7d

Comment by Githook User [ 04/Sep/15 ]

Author:

{u'username': u'rozza', u'name': u'Ross Lawley', u'email': u'ross.lawley@gmail.com'}

Message: Fix Async Streams timeout behaviour

AsynchronousSocketChannelStream no longer wraps open or timeout exceptions
Netty now respects the read timeout setting correctly.

JAVA-1934
Branch: 3.0.x
https://github.com/mongodb/mongo-java-driver/commit/9cff218528cbbe31b7e5db5644321294a533da65

Comment by Githook User [ 04/Sep/15 ]

Author:

{u'username': u'rozza', u'name': u'Ross Lawley', u'email': u'ross.lawley@gmail.com'}

Message: Fix Async Streams timeout behaviour

AsynchronousSocketChannelStream no longer wraps open or timeout exceptions
Netty now respects the read timeout setting correctly.

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

Comment by Githook User [ 04/Sep/15 ]

Author:

{u'username': u'rozza', u'name': u'Ross Lawley', u'email': u'ross.lawley@gmail.com'}

Message: Fix Async Streams timeout behaviour

AsynchronousSocketChannelStream no longer wraps open or timeout exceptions
Netty now respects the read timeout setting correctly.

JAVA-1934
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/60cdedc85e52114eedd5740e60f67cb2a14079cc

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