Mysql Timeouts with RP2.2

Hello,

I am having the same error experienced in older RS versions with MySQL timeouts.

http://forum.reportserver.net/viewtopic.php?id=98

I have tried looking for the pool.cf file, but cannot find it on RS2.2.1-5602

OK, I have found the pool file under the File system in Administrator (I was looking for it in the OS).

This is the pool configuration

<?xml version="1.0" encoding="UTF-8"?> 40 10 10 500 60000 7200 3600

This is the error I get

Error: An error occured during report execution.
The report could not be executed: Could not open connection to: jdbc:mysql://172.31.254.62:3306/portal210 with user: {username}. java.sql.SQLNonTransientConnectionException: Could not read resultset: unexpected end of stream, read 0bytes from 4
To get help please contact an administrator.
Details
net.datenwerke.rs.core.service.reportmanager.exceptions.ReportExecutorException: The report could not be executed: Could not open connection to: jdbc:mysql://{serverip}:3306/portal210 with user: {username}. java.sql.SQLNonTransientConnectionException: Could not read resultset: unexpected end of stream, read 0bytes from 4 at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:218) at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:119) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet.exeucteReport(ReportExportServlet.java:527) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet.doExportReport(ReportExportServlet.java:402) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet.exportReport(ReportExportServlet.java:333) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet.exportReportById(ReportExportServlet.java:270) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet.exportReportByIdViaRequest(ReportExportServlet.java:261) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet.doGet(ReportExportServlet.java:162) at

I click the refresh (sometimes twice) and it loads the report fine.

Hi,

did you check the value of the wait_timeout property for your mysql server? You can do this with the query

show variables like "wait_timeout"

the default value is 28800 (8hrs) which is way more than the maxConnectionAge the pool uses, so there should be no problems. But perhaps your server just isn’t using the default value.

Cheers,
Thorsten

My value was 15!

I have change it to 3600 and will monitor.

Thank-you