We are running SonarQube 6.7.5 with MySQL Community Edition 5.6.34. We noticed that CPU spiked from 8% (average) to 65% and that Garbage collection was taking place. We thought that the messages in the web.log were causing the issue, so we did a restart but are still seeing these errors but it is pointing to different RowDataDynamic id’s in the logs. Has anyone seen this before? Could this be the culprit? or is this just “noise” since it is a WARN message?
Error updating database. Cause: java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic@775b7f48 is still active. No statements may be issued when any streaming result sets are open and in use on a given connection. Ensure that you have called .close() on any active streaming result sets before attempting more queries.
The error may involve org.sonar.db.es.EsQueueMapper.delete-Inline
The error occurred while setting parameters
Cause: java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic@775b7f48 is still active. No statements may be issued when any streaming result sets are open and in use on a given connection. Ensure that you have called .close() on any active streaming result sets before attempting more queries.
We stopped supporting MySQL starting with SonarQube 7.9 LTS, because of performance issues. I suggest you to upgrade at your early convenience, upgrading first to SonarQube former LTS 6.7.7, migrate to PostgreSQL/Oracle/MsSQL, then upgrade to SonarQube current LTS 7.9.2.