Underlying Connection closed

[Wayne Bouwmeester]

Hey fellow .net -> CMS developers,

Every once in a while, when running a longer process form a .net page
against the CMS web services, I get the error (WebException): "The
underlying connection was closed: An unexpected error occurred on a
receive"
If I get it while running in debug mode, the code breaks on the error,
and I can simply enable editing, are continue running the code.

Any ideas what this means? It's not Login/Session related because I
can continue running with the same login and session, but it means I
need to trap the error, and resume as if there isn't one if it occurs.

Wayne.

[markus giesen]

Are you connecting to a Oracle database or SQL?
Some Oracle versions seem to "bump out" for a while and then continue
working as usual..
Either that or it's a glitch in the Matrix ;)

On 27 Aug., 00:15, Wayne Bouwmeester <wayne.bouwmees...@gmail.com>
wrote:

[Wayne Bouwmeester]

The CMS is on SQL. I'm not trying to connect to the DB though. The
error comes from the CMS RQL web service.
I'd call it a glitch if it only happened once, but I reserve
"gremlins" for this one.
It happens often enough - especially when the server starts to get
"tired" and needs a reboot.

[TonyGayter]

Two things to check for if your running off the services (the
exception handling from these are rubbish). Firstly the asp timout
kicks in if a process takes longer than 60 seconds (by default), In
my .net pages I grab teh current timeout, then set it to a much longer
time, then in page unload I reset it back to default timeout. I will
get an example whne I get ack to work in a bit.

Also you might need to make the buffer size larger for the xml
returned by teh services as rql is very verbose and can return a lot
of information.




On Aug 27, 5:43 am, Wayne Bouwmeester <wayne.bouwmees...@gmail.com>
wrote:

> > > Wayne.- Hide quoted text -
>
> - Show quoted text -