In my application server i have the TROSuperTCPServer, if stop (deactive) and start (Active) the SuperTCPServer my client application don’t connect, show message : An exception was raised on the server: Session {XXXX} could not be found..
If i close server application and open it’s OK and works.
EvgnyK, after stop and start SuperTCPServer the SessionManager don’t reconize new sessions created by ServiceLogin. It’s possible restart SessionManager with SuperTCPServer ?
I can’t reproduce this issue with simple testcase
I’ve used SuperTCP Channel Chat sample.
just drop button to form and add
procedure TSuperTCPChannelChat_ServerMainForm.Button1Click(Sender: TObject);
begin
ROServer.Active := not ROServer.Active;
Caption := 'server.active is '+BoolToStr(ROServer.Active, True);
end;
after pressing to button twice, send message from client, it will show error similar to your one, click logoff and logon an it works again as expected, so I think, this situation isn’t handled correctly in your client
On my application server that was migrated from DataSnap to RemObject, we had this feature of restarting the application server without needing to close the application. But with RemObjects it looks like this is not possible. This way we have chosen to remove this functionality from the application server.