On Mar 25, 2010, at 18:33, Jon Robertson wrote:
Does anyone know why ASyncReceive is swallowing the exception and not
calling HandleBackgroundException?
Wow, that was a some time ago. As far as I recall, Arno and I verified that it
was indeed a bug; the code should be trapping exceptions
Message -
From: DZ-Jay d...@caribe.net
To: ICS support mailing twsocket@elists.org
Sent: Friday, March 26, 2010 10:14 AM
Subject: Re: [twsocket] Exceptions ignored in OnDataAvailable method
On Mar 25, 2010, at 18:33, Jon Robertson wrote:
Does anyone know why ASyncReceive is swallowing
Jon Robertson wrote:
FWIW, I've patched the exception handler in ASyncReceive as below. If there
are objections, please explain them so I can determine another solution.
except
on E:Exception do begin
bMore := FALSE;
HandleBackGroundException(E);
My service, which communicates using ICS, is flakey for some customers.
I've got quite a bit of exception handling and logging, and there was
nothing indicating an exception was occurring.
I finally pinpointed an exception that one customer was getting. I hooked
TWSocket.OnDataAvailable and was
DZ-Jay wrote:
On Dec 1, 2007, at 13:36, Arno Garrels wrote:
Have you got any exception that was raised from TWSocket internaly?
I mean outside of your handler?
Well, I noticed the issue because my handler raised an unhandled
exception and the application then behaved in a strange manner
DZ-Jay wrote:
Hello:
In the TWSocket component, I've noticed that if an exception is thrown
within an OnDataAvailable handler
(which is triggered from TCustomWSocket.ASyncReceive() method) they
will be ignored, and only the bMore flag is set to false which will
stop the receive loop.
Have
On Dec 1, 2007, at 13:36, Arno Garrels wrote:
Have you got any exception that was raised from TWSocket internaly?
I mean outside of your handler?
Well, I noticed the issue because my handler raised an unhandled
exception and the application then behaved in a strange manner because
it was