New answers tagged jdbc
Have you tested or would it be possible to drop indexes on the destination DB table(s) where you are inserting into, insert those into smaller batched chunks (optimal as indicated above), and then rebuild the indexes on the destination table(s) once all inserts are complete? May be something easy enough to test to confirm.
I think this link will be of some help to you with max connections. How to get rid of "maximum user connections" error ? (if you end up copying and pasting the instructions, not that connections is misspelled in the first SQL statement). Run SHOW VARIABLES LIKE '%max%conn%'; against your database and see what your relevant variables are set at ...
Go into my.cnf (or my.ini). Increase (or set) max_user_connections in the [mysqld] section. Also check max_connections; the 197 may be bumping up against that. Do you really have a single user connecting more than 40 times? Or is the "connection pooling" inflating things?
Consider batching your commits. A batch size of 1024 is a good starting size. Change batch sizes until you reach your optimum throughput.
Doesn't look like an issue with SQL Server. Here's a link which talks about connection being forcibly closed by sql server : https://technet.microsoft.com/en-us/library/ms187005(v=sql.105).aspx Also, the following post might help you analyze the error further : ...
Top 50 recent answers are included