java.sql.SQLException: Streaming result set > com.mysql.jdbc.RowDataDynamic@32d051c1 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.


Samebug tips

MySQL doesn't support some types of characters (such as emojis) with the utf8 encoding. You need to be on MySQL 5.5+ and force utf8mb4 (everywhere, client and server). You can do this sending the query "SET NAMES utf8mb4". Check this https://goo.gl/3E2qzg


7 months ago
Expert tip

Solutions on the web

Solution icon of web
via nabble.com by Unknown author, 8 months ago
Streaming result set > com.mysql.jdbc.RowDataDynamic@32d051c1 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.

Solution icon of web
via grokbase.com by Unknown author, 1 year ago
Streaming result set com.mysql.jdbc.RowDataDynamic@1a797305 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.

Solution icon of web
via grokbase.com by Unknown author, 1 year ago
Streaming result set com.mysql.jdbc.RowDataDynamic@71f18c82 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.

Solution icon of stackoverflow
Parameter index out of range (1 > number of parameters, which is 0). null

Solution icon of stackoverflow
Streaming result set com.mysql.jdbc.RowDataDynamic@2d749418 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.

Solution icon of web
Streaming result set com.mysql.jdbc.RowDataDynamic@1cfabc3a 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.

Solution icon of github
via GitHub by mibby
, 1 year ago
Streaming result set com.mysql.jdbc.RowDataDynamic@131d5581 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.

Solution icon of stackoverflow
via Stack Overflow by Kishore Bhosale
, 1 year ago
Streaming result set com.mysql.jdbc.RowDataDynamic@70ba428e 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.

Solution icon of web
Streaming result set com.mysql.jdbc.RowDataDynamic@10d95cd 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.

Solution icon of web
Streaming result set com.mysql.jdbc.RowDataDynamic@1cfabc3a 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.

Stack trace

java.sql.SQLException: Streaming result set

> com.mysql.jdbc.RowDataDynamic@32d051c1 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:926)
	at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:923)

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
160 more bugmates