Archived
This forum has been archived. Please start a new discussion on GitHub.
server activation options
Hello,
By on-demand server activation, is it the case that when a client first calls a server, it is started, the client's command processed and then it is shutdown again only to be reactivated once the client makes another call?
The reason I ask is that we have private variables which of course lose their contents everytime the sever is activated. We see that this activation seems to take place everytime the client calls the server. (We see the following: TIMESTAMP Activator: detected termination of server... and then TIMESTAMP Activator: activating server ...).
How can we unsure that the server is activated with the first client request and stays activated until the client itself shuts down?
Thank you for your time.
By on-demand server activation, is it the case that when a client first calls a server, it is started, the client's command processed and then it is shutdown again only to be reactivated once the client makes another call?
The reason I ask is that we have private variables which of course lose their contents everytime the sever is activated. We see that this activation seems to take place everytime the client calls the server. (We see the following: TIMESTAMP Activator: detected termination of server... and then TIMESTAMP Activator: activating server ...).
How can we unsure that the server is activated with the first client request and stays activated until the client itself shuts down?
Thank you for your time.
0
Comments
-
Hi,
The server is started upon the first client invocation and should remain up until it's explicitly stopped either through an IceGrid admin utility, explicitly by your client or if it remains idle for some time and you've set the Ice.ServerIdleTime property. You can try this out with the demo/IceGrid/simple demo.
Perhaps your server stops because of a crash when executing a method invocation? You should provide more information if you need further help on the issue (seeing the activator trace, enabled with IceGrid.Node.Trace.Activator=2, would help for instance).
Cheers,
Benoit.0 -
Thank you!
We've had everything working with direct proxies and have started to use IceGrid now.. apparently, a small ''waitForShutdown" got lost in the conversion!! So sorry! and thanks again! on-demand is in fact what we are looking for!0
