D
dbeavon
Guest
Can someone tell me how long it takes for PASOE to stop on Windows? We have PASOE registered as a windows service (not sure if the platform matters one way or the other). Registering as a service is accomplished with a tcman command: (tcman service oepas1 register). Once it is registered as a service in windows, it is managed by service control commands (net stop oepas1). Or at least it is supposed to. Under normal circumstances I can use "net stop" commands and the service stops in less than three seconds. But when the service is under load, it refuses to stop, even after thirty seconds. The tomcat service seems to be allowing new, overlapping client requests to arrive and be processed. The tomcat server doesn't seem to interrupt any requests, nor disallow new requests. Can someone please tell me if this is expected behavior? How long until the shutdown process will forcefully disallow new connections? I've already tried to take drastic measures myself to facilitate the shutting down of the service, for example during a shutdown request I've tried to kill msagent processes from the OS. But that doesn't seem to help matters. PASOE will not only *ignore* my shutdown request, but will launch *new* msagent processes to replace the missing ones. How long until PASOE/tomcat actually "gets serious" about shutting down, and it stops taking incoming requests from new clients? What is the protocol for this? Why is the shutdown operation delayed by new client requests? Is the problem related to the integration with the service control manager on windows? Is it necessary to introduce some custom steps to force a shutdown (like using oemanager to stop some PASOE web applications first)? Or maybe I should also be using the tomcat manager API to expire all active HTTP sessions? It would be nice if there was some configuration that says the tomcat process will kill itself off after a predetermined number of seconds, even when clients are connected, and while new clients are attempting to connect. Perhaps the problem is not related to PASOE in particular, but affects *all* tomcat-hosted applications? Google seems to say that other applications which use tomcat can be affected by this issue: tomcat service taking too long to stop - Google Search If anyone else has worked on this problem in the past, I would greatly appreciate some tips on how to forcefully stop the PASOE service in under 30 seconds.
Continue reading...
Continue reading...