Shutdown - Stop accepting new work requests, allow current work to complete, and then Quit. Here is the decumentation for the shutdown command: If a task or a server is in pending shutdown some resources are not available any more and cannot fully controlled terminate pending work.
#Ibm lotus symphony not responding full
If you quit a servertask the task has only limited time to continue to work with full resources available. Yes there is a big difference between using tell traveler quit and tell traveler shutdown! This means it could come to undesired timing issues when HTTP and Traveler do their shutdown at the same time.Ī controlled Traveler server shutdown would be the cleaner solution. Sadly if you shutdown the whole server all processed will receive the quit command at the same time and will start to shutdown.
#Ibm lotus symphony not responding windows
There is no simple solution for Windows because Domino is started as a Windows service.īut if you shutdown your server manually, you should shutdown the Traveler server and also use the notes.ini setting. # - Delay before shutting down the Domino server after invoking the pre-shutdown command. # - Command to execute before shutting down the Domino server -ĭOMINO_PRE_SHUTDOWN_COMMAND="tell traveler shutdown" My Domino start script for Linux allows to configure a pre-shutdown command which can be used to shutdown Traveler before you shutdown the whole server. This is true if you shutdown the Traveler task or also during shutdown of the whole server. It makes sense to configure the server to be either fully available or to not respond to HTTPS requests if the Traveler service is not available. That's an undesirable result for a load-balancer because usually the load-balance does not check for this status and might continue to send devices to that Traveler server.
So if you don't shutdown the HTTP task your load-balancer might still send requests to the Traveler server which reports back that the Traveler Server is not available (" IBM Traveler server is not available."). This is important for Traveler HA environments because the Traveler OSGi servlet will only connect to the local Traveler servertask which will than either process the request or forward it to another Traveler server (if another server holds the master monitor for the user).
If you configure NTS_AUTOSTOP_HTTP=true the Traveler servertask will automatically take care of shutting down the HTTP task in the right moment. When you configured NTS_AUTOSTART_HTTP=true the Traveler task did start the HTTP task automatically but by default the HTTP task will not be shutdown automatically when you just shutdown the Traveler servertask. There is a special Traveler shutdown command " tell traveler shutdown" that can be used to let Traveler finish it's work and not accept any new requests before cleanly shutting down. But even that might lead to undesired results. The better way would be to shutdown the Traveler servertask first. Shutting down the Traveler servertask when the Domino server/service is stopped might lead to hang situations of the HTTP task. Specially on a Traveler HA server this becomes important. Correctly Stopping a Traveler Server Daniel Nashed 24 October 2017 15:02:57 This is not new but I ran into this a couple of times on customer site.