Application manager for a content delivery system

• US 20030028680A1
• Filed: 06/26/2001
• Published: 02/06/2003
• Est. Priority Date: 06/26/2001
• Status: Abandoned Application

• Current Assignee: Stellar One Corp.
• Original Assignee: Stellar One Corp.
• Inventors: Jin, Frank
• Application Number:
  US09/893,351
• Publication Number:
  US 20030028680A1
• Time in Patent Office: Days
• US Class Current: 719/313
• CPC Class Codes: G06F 11/0715 in a system implementing multitasking multitasking per se G06F9/46
• CPC Class Codes: G06F 11/0757 by exceeding a time limit, i.e. time-out, e.g. watchdogs
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: G06F 11/1417 Boot up procedures
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating

Abstract

An applications manager, executed with application resources in a streaming media retrieval system, which monitors selected or registered applications and initiates recovery procedures in the event of an error. An application manager thread is instantiated for each application process to be monitored. The application process is monitored for a state message that is periodically transmitted by the application process. If the state message is not received within a period, the application manager is configured to autonomously initiate one of a number of recovery processes, which range from process-level to operating system-level.

Claims

1. A method for managing application resources in a streaming media retrieval system, comprising:

monitoring a set of application processes for a state message periodically transmitted by each application process; and

if an expected state message is not received from one of the application processes within the period, initiating one of a plurality of recovery processes.

2. A method of monitoring one or more applications running in an application environment, wherein each application executes at least one process, comprising:

monitoring one or more applications for periodic state messages generated by each application process that is running;

when no state message is received, recording an error for the associated application process; and

based on the recorded error, automatically executing one of a plurality of recovery processes.

3. The method of claim 2, wherein monitoring one or more applications for periodic state messages includes implementing a monitor process for each application process thread generated by the application.

4. The method of claim 3, wherein automatically executing one of a plurality of recovery processes includes eliminating the application process thread that has failed, and starting a new application process thread.

5. The method of claim 2, wherein monitoring one or more applications for periodic state messages includes implementing a monitor process for each application process of the application.

6. The method of claim 5, wherein automatically executing one of a plurality of recovery processes includes eliminating the application process that has failed, and starting a new application process.

7. The method of claim 6, further comprising storing a history of the recovery procedure in a memory.

8. The method of claim 6, wherein automatically executing one of a plurality of recovery processes further includes, initiating a logoff from and subsequent logon to the application environment.

9. The method of claim 8, wherein automatically executing one of a plurality of recovery processes further includes rebooting the operating system software that hosts the application environment.

10. The method of claim 5, wherein monitoring one or more applications for periodic state messages further includes implementing a monitor process for all other monitor processes.

11. The method of claim 10, wherein automatically executing one of a plurality of recovery processes further includes initiating a hardware reset via the operating system software.

12. The method of claim 11, wherein automatically executing one of a plurality of recovery processes further includes initiating a switch to a backup operating system partition.

13. A system for monitoring one or more applications running in an application environment, wherein each application executes at least one process, comprising:

a monitor program having a kernel timer configured to monitor for periodic state messages generated by an application process that is running;

a plurality of recovery procedures, stored as instructions in one or more files associated with the monitor program; and

logic, linked with the monitor program and responsive to the kernel timer when no state message is received, configured to register an error for the associated application process and to automatically execute one of the plurality of recovery procedures based on the error.

14. The system of claim 13, further comprising a memory, in which a history of recovery procedures are stored upon being executed by the logic.

15. The system of claim 13, wherein the plurality of recovery procedures includes instructions to eliminate an application process that has failed.

16. The system of claim 15, wherein the plurality of recovery procedures further includes starting a new application process in place of the eliminated application process.

17. The system of claim 13, wherein the plurality of recovery procedures includes instructions to reboot the operating system that hosts the application environment.

18. The system of claim 17, wherein the plurality of recovery procedures further includes instructions to initiate a hardware reset via the operating system software.

19. The system of claim 13, wherein the monitor program further includes a self-monitoring process.

20. The system of claim 13, wherein the plurality of recovery procedures includes instructions to switch to a backup operating system partition.