[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: |
|
||||||||
| 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
|
| 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
|
| 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
|
| 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
|
| 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
|
| 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
|