# Warning-Error in Gateway console Log **URL:** \ **Category:** Ignition\ **Created:** [February 27, 2013, 5:42pm UTC](https://forum.inductiveautomation.com/t/warning-error-in-gateway-console-log/5932 "2013-02-27T17:42:15Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jim\_lapratt](https://avatars.discourse-cdn.com/v4/letter/j/cc9497/32.png) [@jim\_lapratt](https://forum.inductiveautomation.com/u/jim_lapratt)\ **Post date:** [February 27, 2013, 5:42pm UTC](https://forum.inductiveautomation.com/t/warning-error-in-gateway-console-log/5932/1 "2013-02-27T17:42:15Z")
I keep getting this error showing up in the log, What is possible problem? [WARN] 12:37:17 PM RunQuery Error closing statement. java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic@5372b9a5 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. at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:934) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:931) at com.mysql.jdbc.MysqlIO.checkForOutstandingStreamingData(MysqlIO.java:3236) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2399) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2671) at com.mysql.jdbc.StatementImpl.executeSimpleNonQuery(StatementImpl.java:1644) at com.mysql.jdbc.RowDataDynamic.close(RowDataDynamic.java:196) at com.mysql.jdbc.ResultSetImpl.realClose(ResultSetImpl.java:7335) at com.mysql.jdbc.ResultSetImpl.close(ResultSetImpl.java:909) at org.apache.commons.dbcp.DelegatingResultSet.close(DelegatingResultSet.java:152) at org.apache.commons.dbcp.DelegatingStatement.close(DelegatingStatement.java:163) at com.inductiveautomation.ignition.gateway.datasource.DelegatingStatement.close(DelegatingStatement.java:39) at com.inductiveautomation.ignition.gateway.datasource.SRConnectionWrapper$SRStatement.close(SRConnectionWrapper.java:535) at com.inductiveautomation.ignition.gateway.servlets.gateway.functions.AbstractDBAction.invoke(AbstractDBAction.java:87) at com.inductiveautomation.ignition.gateway.servlets.Gateway.doPost(Gateway.java:398) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at com.inductiveautomation.ignition.gateway.bootstrap.MapServlet.service(MapServlet.java:85) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:722) ---
**Author:** ![greg.simpson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/greg.simpson/32/3135_2.png) [@greg.simpson](https://forum.inductiveautomation.com/u/greg.simpson)\ **Post date:** [February 27, 2013, 5:49pm UTC](https://forum.inductiveautomation.com/t/warning-error-in-gateway-console-log/5932/2 "2013-02-27T17:49:07Z")
What version of Ignition, and Java are you using? What version of MySQL are you using? ---
**Author:** ![jim\_lapratt](https://avatars.discourse-cdn.com/v4/letter/j/cc9497/32.png) [@jim\_lapratt](https://forum.inductiveautomation.com/u/jim_lapratt)\ **Post date:** [February 27, 2013, 7:05pm UTC](https://forum.inductiveautomation.com/t/warning-error-in-gateway-console-log/5932/3 "2013-02-27T19:05:33Z")
Ignition: 7.5.5-b1255 Java: Oracle 1.7.0\_15 MySql: 5.5.29 Sorry ☹ ---
**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\ **Post date:** [February 27, 2013, 10:41pm UTC](https://forum.inductiveautomation.com/t/warning-error-in-gateway-console-log/5932/4 "2013-02-27T22:41:11Z")
Hi, I think we’ve tracked down the issue. I don’t think it’s a serious problem, just an annoyance, but it should be taken care of in the next update. Out of curiosity, did you manually update the mysql jdbc driver? I’m just trying to figure out why more people don’t see this error. Regards, ---
**Author:** ![jim\_lapratt](https://avatars.discourse-cdn.com/v4/letter/j/cc9497/32.png) [@jim\_lapratt](https://forum.inductiveautomation.com/u/jim_lapratt)\ **Post date:** [February 28, 2013, 1:33pm UTC](https://forum.inductiveautomation.com/t/warning-error-in-gateway-console-log/5932/5 "2013-02-28T13:33:21Z")
Yes we did. Current : 5.1.19 I see that 5.1.23 is out Hmmm… Should I update or not…Hmmm ---
**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\ **Post date:** [February 28, 2013, 4:18pm UTC](https://forum.inductiveautomation.com/t/warning-error-in-gateway-console-log/5932/6 "2013-02-28T16:18:08Z")
Hi, I wouldn’t worry about updating again. I think they simply decided to take something that could be construed as incorrect usage and actually make it an error. We weren’t closing a certain object, but were closing its parent. It shouldn’t result in any kind of real leak, but I guess that depend on the implementation of the driver, so it’s best to fix it. I believe the fix should make it into the 7.5.6 update. Regards,