Methods and apparatus for managing deactivation and shutdown of a server
May 25, 2016. Estimated Expiration Date is calculated based on simple USPTO term provisions. It does not account for terminal disclaimers, term adjustments, failure to pay maintenance fees, or other factors which might affect the term of a patent.Patent ReferencesWaitable object creation system and method in an object based computer operating system Conditional object creating system having different object pointers for accessing a set of data structure objects Temporary object handling system and method in an object based computer operating system Server impersonation of client processes in an object based computer operating system System for garbage collecting unused memory space represented by a digraph by assigning values of node identifiers to selected variables based upon predetermined conditions Object transferring system and method in an object based computer operating system System for determining the rights of object access for a server process by combining them with the rights of the client process Cooperative processing interface and communication broker for heterogeneous computing environments File based and highly available hybrid database Rendering context manager for display adapters InventorApplicationNo. 408627 filed on 03/22/1995US Classes:709/203Client/serverExaminersPrimary: Toplu, Lucien U.Assistant: Park, Alice Y. Attorney, Agent or FirmForeign Patent References
International ClassG06F 013/00AbstractA number of methods and apparatus for managing clients of a computer server. In particular, the usher implements an orderly and predictable server deactivation and/or shut down strategy in generally the following manner. The usher continuously maintains a transaction counter indicative of the number of clients actively utilizing services. For example, the usher may increment the transaction counter when a service is requested and then decrement the transaction counter when a service is completed or terminated. However, at some point in the server operation, the usher may receive a lock up request. This may occur because a client has invoked a deactivation and/or shut down operation, or the server may decide to shut down itself. In any event, upon receiving the lock up request, the usher will not perform any new client requests. Thus the usher controls the accessibility of the server to external clients by preventing new client requests for service in preparation for shut down. Nevertheless, the usher utilizes a gentle strategy and only eliminates clients through attrition. Hence the usher implements a shut down strategy which, while not accepting new client requests, will complete any services active at the time deactivation and/or shut down was requested. In some embodiments of the present invention, an usher is an internal component of or is used by a server such as a computer process, a computer service, or a target object.Other References
| |
