| Bug #115449 | NativePacketPayload.readInteger causes ArrayIndexOutOfBoundsException | ||
|---|---|---|---|
| Submitted: | 27 Jun 2024 14:07 | Modified: | 16 Jul 2024 10:34 |
| Reporter: | giacomo petronio | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | Connector / J | Severity: | S2 (Serious) |
| Version: | 8.2.0 | OS: | Any |
| Assigned to: | Filipe Silva | CPU Architecture: | Any |
[15 Jul 2024 23:29]
Filipe Silva
Hi Giacomo, Thank you for your interest in MySQL Connector/J and for taking the time to report this issue. Can you please provide the answers for following questions? 1. Are you using MySQL Router in this production database? If so, any difference if you connect directly to the database? 2. What version of the MySQL Server are you using? 3. In what OS is the MySQL Server and Connector/J running? 4. Please test with latest MySQL Connector/J version. If getting the same result, does it help if you add "trackSessionState=true" to the connection string? 5. Without a self-contained test case it will be near to impossible to reproduce the issue. Are you able to provide a self-contained test case that fails on any environment? Thanks,
[16 Jul 2024 8:39]
giacomo petronio
1. We are not using MySQL Router. We connect directly to the database 2. The version of MySQL Server is MySQL 5.7.44 (managed by Google Cloud) 3. MySQL Server is running on a Linux server, since it's completely managed by GCP, there is no easy way to find out the OS. We have the same issue running the connector from both Linux (CentOS 7) and Windows 11 4. We tested with various Connector versions (8.0.29 8.0.33 8.1.0 8.2.0 8.3.0), including the latest one 9.0.0 always with the same results. Adding trackSessionState=true to the connection string does not change the outcome. 5. Sadly the problem occurs only in the production server, we are not able to reproduce the error in other MySQL server, even using the same data with a dump/restore
[16 Jul 2024 10:34]
Filipe Silva
Unfortunately there's nothing we can do about this at this point. MySQL Server 5.7 is no longer a maintained version--it is EOL since October 25, 2023, so the risk of hitting incompatibilities between the server and the connectors becomes higher every new release, which may not be exactly your case since you tested with drivers from the same time period. However, since you are unable to come up with a reproducible test case it would be close to impossible for us to figure out what's going on and to know what to fix. Note that the exception hints that the data coming from the server somehow got "damaged" before reaching the connector. It could be the server encoding it in ways the connector no longer expects, it could be the connector is enabling features by default the server doesn't support and as a result the decoding ended up messed up, it could simply be that the data is getting corrupted on the wire, or something else. If you find ways of reproducing the problem consistently in a system we may replicate, then please re-open this report or file a new bug providing all the information. Meanwhile I'll be forced to close this report as "Can't repeat".
Description: We have the following error every time we execute a simple specific stored procedure returning a ResultSet. Stacktrace java.sql.SQLException: Index 5 out of bounds for length 5 at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:130) at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122) at com.mysql.cj.jdbc.ClientPreparedStatement.executeInternal(ClientPreparedStatement.java:912) at com.mysql.cj.jdbc.ClientPreparedStatement.execute(ClientPreparedStatement.java:354) at com.mysql.cj.jdbc.CallableStatement.execute(CallableStatement.java:848) at eu.o3e.main.TelemedicineTest.main(TelemedicineTest.java:22) Caused by: java.lang.ArrayIndexOutOfBoundsException: Index 5 out of bounds for length 5 at com.mysql.cj.protocol.a.NativePacketPayload.readInteger(NativePacketPayload.java:394) at com.mysql.cj.protocol.a.NativePacketPayload.readInteger(NativePacketPayload.java:408) at com.mysql.cj.protocol.a.NativePacketPayload.readBytes(NativePacketPayload.java:524) at com.mysql.cj.protocol.a.TextRowFactory.createFromMessage(TextRowFactory.java:65) at com.mysql.cj.protocol.a.TextRowFactory.createFromMessage(TextRowFactory.java:42) at com.mysql.cj.protocol.a.ResultsetRowReader.read(ResultsetRowReader.java:87) at com.mysql.cj.protocol.a.ResultsetRowReader.read(ResultsetRowReader.java:42) at com.mysql.cj.protocol.a.NativeProtocol.read(NativeProtocol.java:1648) at com.mysql.cj.protocol.a.TextResultsetReader.read(TextResultsetReader.java:81) at com.mysql.cj.protocol.a.TextResultsetReader.read(TextResultsetReader.java:48) at com.mysql.cj.protocol.a.NativeProtocol.read(NativeProtocol.java:1661) at com.mysql.cj.protocol.a.NativeProtocol.readAllResults(NativeProtocol.java:1713) at com.mysql.cj.protocol.a.NativeProtocol.sendQueryPacket(NativeProtocol.java:1063) at com.mysql.cj.NativeSession.execSQL(NativeSession.java:660) at com.mysql.cj.jdbc.ClientPreparedStatement.executeInternal(ClientPreparedStatement.java:889) ... 3 more We tried with the following connectors, always with the same outcome: implementation files("lib/mysql-connector-java-8.0.29.jar") implementation files("lib/mysql-connector-j-8.0.33.jar") implementation files("lib/mysql-connector-j-8.1.0.jar") implementation files("lib/mysql-connector-j-8.2.0.jar") implementation files("lib/mysql-connector-j-8.3.0.jar") With the following connector, no exception is thrown but the obtained ResultSet is not null but is empty (and it should not be empty) implementation files("lib/mysql-connector-java-8.0.11.jar") With mariadb connector (mariadb-java-client-3.4.0.jar) the stored procedure works fine How to repeat: It happens only in a managed (GCP) production database (5.7.44-google-log) Restoring a backup of the same data on a different database instance is not enough to replicate the problem We are able to raise the exception with the following code: import java.sql.CallableStatement; import java.sql.Connection; import java.sql.DriverManager; import java.sql.ResultSet; import java.sql.SQLException; public class Test { private static final String JDBC_URL = "jdbc:mysql://xx.xx.xx.xx:3306/schema"; private static final String JDBC_USER = "user"; private static final String JDBC_PASSWORD = "***********"; public static void main(String[] args) { try (Connection connection = DriverManager.getConnection(JDBC_URL, JDBC_USER, JDBC_PASSWORD)) { String storedProcedure = "{ CALL problematicStoredProcedure() }"; try (CallableStatement callableStatement = connection.prepareCall(storedProcedure)) { boolean hasResultSet = callableStatement.execute(); // Exception is thrown HERE if (hasResultSet) { try (ResultSet resultSet = callableStatement.getResultSet()) { while (resultSet.next()) { int pk = resultSet.getInt(1); String name = resultSet.getString(2); System.out.println("PK: " + pk + ", Name: " + name); } } } } } catch (SQLException e) { e.printStackTrace(); } } }