[69350 Open] EIPSocketError 'Cannot accept connection' when destroy server

Hi

We upgraded to XE6 + 8.0.81 Remobjects + new powerful workstations. Since that moment we do run into
EIPSocketError with message 'Cannot accept connection’
when I destroy the RO-Server components.

It’s a silent crash in a WorkThread but always shown in my Delphi Debugger.
For me it seems to be a timing problem as it does not occur all the time.

I prepared a very simple app that reproduces the problem (at least on our very fast new workstations).
Just send me a notice where I shall upload the sample.

regards

Günther Schoch / www.gs-soft.com

hi, you can send it directly to support@ or attach it here

20140829_WorkerThreadException.zip (157.6 KB)

thank, uploaded now.

regards

Günther

I’m sorry, but I can’t reproduce this issue. looks like you have a very powerful workstations.

btw, FROHTTPServer isn’t destroyed in testcase.

btw, FROHTTPServer isn’t destroyed in testcase.

procedure TWebServiceServer.StopServer; // called within the destroy
begin
if Assigned(FROHTTPServer) then
FROHTTPServer.Active:= False;
FreeAndNil(FROHTTPServer);

should destroy

but I can’t reproduce this issue.

I attached a new version including a loop … just press the button about 3 times (each does fire 20 tests). If you do not run into the problem than let me know - we would then setup a WebEx session that you can debug within our environment.

best regards, Günther

20140901_WorkerThreadException.zip (56.4 KB)

Thanks, logged as bugs://69350: TROIpHTTPServer: EIPSocketError when server started and stopped at once

Means that you were able to reproduce the problem with our sample?

yes, I’ve reproduced EIPSocketError exception with your 2nd sample.

Was this ever solved? I’ve noticed that, when running inside the IDE, I also get this exception and message when shutting down the server. Only appears in the IDE and doesn’t cause any harm so not really important, just found this thread and wondered if there was any solution?

#69350 isn’t solved yet
you can try to use other http server (TROIndyHTTPServer or TROWinHttpServer) if this case (stopping server after it was started) can be applied to your case

Nah it’s not a big problem at all, I was just wondering :slight_smile: