[MXS-1123] connect_timeout setting causes frequent disconnects Created: 2017-02-06 Updated: 2017-03-07 Resolved: 2017-02-11 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 2.0.3 |
| Fix Version/s: | 2.0.5 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Kyle Joiner (Inactive) | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
When a connect_timeout is specified clients connected to maxscale are frequently disconnected earlier than the timeout value. |
| Comments |
| Comment by markus makela [ 2017-02-06 ] |
|
When one service has idle connection timeouts enabled, other services are also checked. The default value for the idle timeout value limit is LONG_MAX which happens to get multiplied by 10 so that it is scaled correctly. This causes the integer to overflow and the resulting value will always be smaller than the time interval between client actions. All connections to services without the connection_timeout parameter would be closed immediately. A temporary fix to this is to set the value of connection_timeout to a very large value e.g. connection_timeout=8640000. |
| Comment by Johan Wikman [ 2017-02-07 ] |
|
Downgrading to minor as there is a temporary fix. |