I have some questions, there some beahviour still cant correct.
A client connect to the server gte a session GUID, and register for an event.
The server close.
The server open.
How can i make the client reutilice the old GUI painless?
Other scenario. Client close without unregister from the event. What happen with that? Will the server try to send every event to that client app or will auto clean?
Ok, so the client while connected ask the server for events. If server is down, raise some exception? Or ignore the problem in silence?
I save sessions i deb, The problem is the server after restart seems not to load previous sessions, and the customer raises an exception saying the session guid dont exist on the server.
The only requiremente is to load session ids on the sessionmanager at start? Thats all? Im doing something wrong then.
“client will receive all his events after server’s restart.” → dont get that. How the server saves in db events? Anyway i dont like this. I prefer to the server only send the actual events, getting. a lot of previous events have no sense in my business model.
it depends on you: you can process exception in OnPollException event of TROEventReceiver otherwise it will be ignored silently.
what exactly SessionManager are you using? DB SessionManagers should work w/o any problem after restarting server. runtime SessionManagers like InMemory, etc of course will be empty after restarting of server.
DB EventRepositories store data that should be sent to client in DB, so client can receive it in any time while session is valid
You can assign to Application.OnException your own handler of unhandled exceptions if you don’t want to control it in thousand places
I’d suggest to connect to server in Login method. in ROChannelException you can add some handling of such exception too like control state (connected/disconnected), etc.
Can please share the recomended code for solve that problem? Again i have a lot of unable to connect to remote servers after a few days the server running. I have anothe rserver processor working fine, so the problems seems to be the Ro component server only. I try both Indy and Synape servers. Delphi tokyo 10.2.3 and latest DA beta.
can you create a simple testcase that demonstrates this issue, pls?
I think, solution will be quite trivial because you could miss something obvious
you can attach it here or send directly to support@
Evgeny,
The problem is not at cliente side. When that happens you cant contact the server from any computer (simple testing http://serverip:portofserver/bin returns cannot connect to server)
So, how can i debug that problem at server side? What can cause an indy http server to stop alone?
hmm, try to launch server under debugger and wait for case when doesn’t respond to http://serverip:portofserver/bin
it could be a problem in native indy http server.