Bug #86363 | JDBC socket timeout set to 15ms regardless of uri settings | ||
---|---|---|---|
Submitted: | 17 May 2017 19:34 | Modified: | 18 May 2017 18:00 |
Reporter: | Joseph Gleason | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | 5.1.42 | OS: | Debian |
Assigned to: | CPU Architecture: | Any |
[17 May 2017 19:34]
Joseph Gleason
[18 May 2017 10:45]
Chiranjeevi Battula
Hello Joseph Gleason, Thank you for the bug report. I tried to reproduce the issue at my end using MySQL Connector / J 5.1.42 and MySQL 5.7.18 but not seeing any issues in connectTimeout and socketTimeout. Could you please provide repeatable test case (exact steps, sample test case, database/create table statements, full stack trace etc. - please make it as private if you prefer) to confirm this issue at our end? Thanks, Chiranjeevi.
[18 May 2017 18:00]
Joseph Gleason
And I am an idiot. The short timeout was coming from a connection pooling library that I just copied from another project. I only actually looked at that code when I was looking at it to try to make a minimal reproduction. props.put("socketTimeout", "15"); I will go laugh at myself now. Thanks for your time.