Yesterday, my colleague discovered this error when calling the database stored procedure through JDBC. After more than an hour of troubleshooting, under the reminder of colleagues, I totally understand the root of this mistake. Just in the SQL Server stored procedure, multiple operations are performed, in which the database is considered to have multiple result sets. (The operation affects the number of row databases, it is considered to be a result set), so it is possible to add such a sentence when the stored procedure begins. Set NoCount ON - Close the number of rows that returned
