The whole issue pertains to the transaction, I think that much as been established.  But we will try and come up with a solid scenario so we can really prove it out.

Trent,

Thanks for the update. I'll wait to see what you find out.

Larry:

We are going to take a different approach here.  We are going to try and replicate your scenario first and see if we can get it to fail.  Once we can get it to fail then it is an easy next step to get you a solution.  So give us a day or two and we are going to try and create a sample that fails in a lab setting so that we can make sure that we are on the same page.  We may send you an email or two if we can't replicate it.  Thanks for your patience.

It should have been in your build, but let's make sure that you have the most recent assemblies.  I am going to create a package file and send it to you here in a bit.

Was a fix for this ever found? I'm on version 1.7.7.7 and it's still happening.

Hi Ben,

Sorry to hear your Thanksgiving wasn't that great. If it helps resolve the issue I'm running the latest version of the framework and ES. Before I posted the problem I download the manual update for ES and re-installed it on the server.

-Larry

Sorry for the delay, Larry.  I was out on vacation when you posted your first question and Trent was holding down the fort.  Then, I was up-chucking all Thanksgiving week.

??????

Any update on this?

To simplify things I created a test application that eliminates my inherited business layer and cuts the number of business objects down to two. What I've found out from running the test application and looking at the database server is that it appears that when saving on a transaction, the ES server tries to obtain one pooled connection for every record. The parent/child relationship doesn't make a difference. If I have 99 parent records and 0 child records everything works fine. But when the parent record count exceeds the maximum number of pooled connections (100 on my server), the save will likely fail and the failure happens when the connection timeout is reached, which I've configured to be 45 seconds. I say likely because 101 may eventually save but 200 will always fail.  When there are both parent and child records, the error begins to occur when the total record count exceeds 100.