This topic is locked
[SOLVED]

 Import error and connection pool size

7/21/2017 2:44:25 PM
ASPRunner.NET General questions
T
Tim author

Hello,
I'm having an issue with importing. It appears that when a record errors on import, a new DB connection is created and the previous one is not closed. I can see this when I query my DB server as the import is in progress. With each error, the total connections goes up by 1. If there are more than 100 records that error, the web app throws a "time out. connection pool max reached" error. I realize it'd be nice if the import file didn't have more than 100 records that error, but sometimes it does (these imports are more than 30K records).
Is there anything that can be done about this issue? Do I have to create a custom connection and set the max connection higher? Or should the import process be releasing these connections when an error occurs?
Thanks,

Tim

T
Tim author 7/26/2017

Fixed in latest release.