ASP.Net/C# - Oracle Procs - The underlying connection was closed: An unexpected error occurred on a receive.

Hello all.  I am getting an error when an oracle proc I have tries to define an output cursor it errors out and then says in my error log "The underlying connection was closed: An unexpected error occurred on a receive.".  It seems like this might have to do with keep alives or something.  This is hitting a web service.  Any ideas all what I can try.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sbornstein2Author Commented:
It bombs on this definition of my output cursor:

                  oracleParams[19] = new Technicolor.Exhibitor.TrackingDAL.OracleWS.OracleParameter();
                  oracleParams[19].ParameterName = "p_retval";
                  oracleParams[19].Direction = OracleWS.ParameterDirection.Output;
                  oracleParams[19].OracleType = OracleWS.OracleType.Number;

On the direction line.  I then get the error The underlying connection was closed: An unexpected error occurred on a receive.".  
The following will help:

XML & ASP.NET Error:"The underlying connection was closed: Unable to connect to the remote server"

need help desperately. The underlying connection was closed:

underlying connection was closed:unable to connect to remote server exception message


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sbornstein2Author Commented:
well the issue is it seems 90% of the time the calls work fine.  Then depending on the resultset returning it drops if it is a large resultset.  The proc itself though returns on the Web Server box very quick.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.