I've described the environment here (near the bottom of the post):
http://stackoverflow.com/questions/25124613/what-can-cause-a-security-context-token-handle-leak
There is a rare handle problem in ICS:
I haven't seen that error, but for my purposes, having to restart the service
once a month
in both client and server, but these stats are just for
the server.
http://ge.tt/5w9Sy1r1
Thanks,
Doug
-Original Message-
From: RTT [mailto:p...@sapo.pt]
Sent: Wednesday, August 13, 2014 10:48 AM
To: ICS support mailing
Subject: Re: [twsocket] Handle Leak
On 13-08-2014 18:04, Doug Billi
This is from the latest snapshot of ICS V8.
procedure TIcsTimer.UpdateTimer;
begin
KillTimer(FIcsWndControl.Handle, UINT_PTR(Self));
if (FInterval <> 0) and FEnabled and Assigned(FOnTimer) then
if SetTimer(FIcsWndControl.Handle,
Cardinal(Self), FInterval, nil)
I was getting a response from an HTTP Server where the Status was set to 0
(instead of 1xx-5xx). This was causing an exception in my application.
Although this is an error on the server side, shouldn't the code be changed
from:
procedure THttpCli.GetHeaderLineNext;
[...]
FStatusCode :=
