java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic@14fc557 is still active. Only one streaming result set may be open and in use per-connection. Ensure that you have called .close() on any active result sets before attempting more queries.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 843859, 11 months ago
Streaming result set com.mysql.jdbc.RowDataDynamic@14fc557 is still active. Only one streaming result set may be open and in use per-connection. Ensure that you have called .close() on any active result sets before attempting more queries.
via hivmr.com by Unknown author, 1 year ago
Streaming result set com.mysql.jdbc.RowDataDynamic@14fc557 is still active. Only one streaming result set may be open and in use per-connection. Ensure that you have called .close() on any active result sets before attempting more queries.
via Pentaho BI Platform Tracking by Brian Vandenberg, 1 year ago
Streaming result set com.mysql.jdbc.RowDataDynamic@1429cb2 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.
via Pentaho BI Platform Tracking by Brian Vandenberg, 11 months ago
Streaming result set com.mysql.jdbc.RowDataDynamic@1429cb2 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.
java.sql.SQLException: Streaming result set com.mysql.jdbc.RowDataDynamic@14fc557 is still active. Only one streaming result set may be open and in use per-connection. Ensure that you have called .close() on any active result sets before attempting more queries.

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.