Documentation Home
MySQL Connector/J 8.0 Developer Guide
Related Documentation Download this Manual
PDF (US Ltr) - 483.3Kb
PDF (A4) - 485.8Kb
HTML Download (TGZ) - 117.4Kb
HTML Download (Zip) - 136.2Kb


MySQL Connector/J 8.0 Developer Guide  /  Known Issues and Limitations

Chapter 16 Known Issues and Limitations

The following are some known issues and limitations for MySQL Connector/J:

  • When Connector/J retrieves timestamps for a daylight saving time (DST) switch day using the getTimeStamp() method on the result set, some of the returned values might be wrong. The errors can be avoided by using the following connection options when connecting to a database:

            serverTimezone=UTC

  • The functionality of the property elideSetAutoCommits has been disabled due to Bug# 66884. Any value given for the property is ignored by Connector/J.

  • MySQL Server uses a proleptic Gregorian calendar internally. However, Connector/J uses java.sql.Date, which is non-proleptic. Therefore, when setting and retrieving dates that were before the Julian-Gregorian cutover (October 15, 1582) using the PreparedStatement methods, always supply explicitly a proleptic Gregorian calendar to the setDate() and getDate() methods, in order to avoid possible errors with dates stored to and calculated by the server.

  • For MySQL 8.0.14 and later, 5.7.25 and later, and 5.6.43 and later: To use Windows named pipes for connections, the MySQL Server that Connector/J wants to connect to must be started with the system variable named_pipe_full_access_group; see Section 6.9, “Connecting Using Named Pipes” for details.

  • Because Connector/J does not enable connections with TLSv1.2 and higher by default due to compatibility issues, when connecting to servers that restrict connections to use those higher TLS versions, you might encounter com.mysql.cj.exceptions.CJCommunicationsException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate). You need to enable connections with TLSv1.2 and higher versions using the enabledTLSProtocols connection property. See Section 6.7, “Connecting Securely Using SSL” for details.