SYSTEMS AND METHODS FOR SERVER CRASH PREVENTION
Disclosed are methods, systems, and computer-readable medium for preventing system crashes, including loading a resource from a real resource location; receiving a registration request from a resource user; registering the resource user by updating a resource owner registration list to indicate the resource user registration; receiving a first unload request and determining that the resource user is registered by accessing the registration list; upon determining that the resource user is registered, denying the first unload request; generating a stop use request; transmitting the stop use request to the resource user; receiving a deregistration request from the resource user, based on the stop use request; deregistering the resource user by updating the resource owner registration list; receiving a second unload request after deregistering the resource user; and approving the second unload request to unload the resource.
1 - 20 . (canceled)
21 . A system comprising:
at least one memory storing instructions; and
at least one processor executing the instructions to perform operations, the operations comprising:
receiving a first unload request for a resource;
determining that a resource user is registered for the resource;
upon determining that the resource user is registered, denying the first unload request;
receiving a deregistration request from the resource user;
deregistering the resource user;
receiving a second unload request after deregistering the resource user; and
approving the second unload request to unload the resource.
22 . The system of claim 21 , further comprising:
upon denying the first unload request:
generating a stop use request; and
transmitting the stop use request to the resource user.
23 . The system of claim 21 ,
wherein registration or deregistration of the resource user is by updating a resource owner registration list, and
wherein updating the resource owner registration list comprises modifying a binary value associated with the resource.
24 . The system of claim 21 , further comprising deleting the resource from the resource user after deregistering the resource user.
25 . The system of claim 22 , wherein the stop use request is generated based on a project unload.
26 . The system of claim 22 , wherein the stop use request is generated based on an cleanup operation.
27 . The system of claim 22 , wherein the operations further comprise:
receiving a resource use request at the resource user;
determining that the stop use request has been received at the resource user; and
denying the resource use request.
28 . The system of claim 27 , wherein the deregistration request from the user is based on denying the resource use request.
29 . The system of claim 22 , wherein the operations further comprise:
receiving a resource use request at the resource user;
determining that the stop use request has not been received at the resource user; and
denying the resource use request.
30 . A system comprising:
at least one memory storing instructions; and
at least one processor executing the instructions to perform operations, the operations comprising:
receiving a first unload request for a resource;
determining that a resource user is registered for the resource;
upon determining that the resource user is registered, denying the first unload request;
determine a null use of the resource by the resource user;
deregistering the resource user, based on the null use;
receiving a second unload request after deregistering the resource user; and
approving the second unload request to unload the resource.
31 . The system of claim 30 , wherein null use of the resource by the resource user is determined by accessing a use log.
32 . The system of claim 30 , further comprising:
upon denying the first unload request:
generating a stop use request; and
transmitting the stop use request to the resource user.
33 . The system of claim 30 ,
wherein registration or deregistration of the resource user is by updating a resource owner registration list, and
wherein updating the resource owner registration list comprises modifying a binary value associated with the resource.
34 . The system of claim 30 , wherein the operations further comprise deleting the resource from the resource user after deregistering the resource user.
35 . The system of claim 32 , wherein the stop use request is generated based on a project unload.
36 . A system comprising:
at least one memory storing instructions; and
at least one processor executing the instructions to perform operations, the operations comprising:
receiving a first unload request for a resource;
determining that a resource user is registered for the resource;
upon determining that the resource user is registered, denying the first unload request;
determining that the resource user is in a sleep state;
deregistering the resource user, based on the determining that the resource user is in a sleep state;
receiving a second unload request after deregistering the resource user; and
approving the second unload request to unload the resource.
37 . The system of claim 36 , wherein determining that the resource user is in a sleep state is based on one of a null response or a sleep state status response.
38 . The system of claim 36 , wherein determining that the resource user is in a sleep state is based on a sleep state instruction.
39 . The system of claim 36 , further comprising:
upon denying the first unload request:
generating a stop use request;
transmitting the stop use request to the resource user.
40 . The system of claim 36 ,
wherein registration or deregistration of the resource user is by updating a resource owner registration list, and
wherein updating the resource owner registration list comprises modifying a binary value associated with the resource.