[CONJ-627] ConnectTimeout defaults to never.... Created: 2018-07-13 Updated: 2018-09-10 Resolved: 2018-09-03 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | configuration |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.2 |
| Type: | Task | Priority: | Minor |
| Reporter: | Juan | Assignee: | Diego Dupin |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Currently and historically ConnectTimeout defaults to 0, which means the connector never times out when trying to connect to a non-responsive back-end. Although this is easy to change as a specified parameter in the connect string, it would make a lot of sense for the connector to default this to a finite value. We have had support issues where the combination of this default and back-end behavior made non-responsive back-end connections basically lock up the connectors trying to reach them, for example. The current connector defaults the value to 10 for aurora configuration, but leaves it at 0 for others. |
| Comments |
| Comment by Diego Dupin [ 2018-09-03 ] |
|
The description is erroneous, my bad. The option "ConnectTimeout" default to 30 seconds since 2.1.2. It was previously set to 0 = no timeout. (MySQL driver default to 0). (Confusion was with socketTimeout that default to 10 seconds for aurora only, 0 for other) |