Method and system for error detection in a managed application environment

• US 6,892,331 B2
• Filed: 01/17/2002
• Issued: 05/10/2005
• Est. Priority Date: 01/17/2002
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Nusbickel, Wendi L., Da Palma, William V., Lucas, Bruce D.
• Primary Examiner(s): BADERMAN, SCOTT T
• Application Number:
  US10/052,454
• Publication Number:
  US 20030135781A1
• Time in Patent Office: 1,209 Days
• Field of Search: 714/23, 714/55, 709/100, 709/101, 709/104, 709/106
• US Class Current: 714/55
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software

Abstract

A method of managing at least one client computer program in a managed application environment can include receiving a request from at least one of a plurality of client computer programs to begin a timer. The timer can correspond to an identified task of the client computer program which has been identified as a time-out susceptible task, and which is executing within a particular thread of execution of the client computer program. The timer corresponding to the request and the time-out susceptible task can be selectively started in a separate thread of execution. The identified task can be timed. If the timer expires, a recovery action can be performed corresponding to the time-out susceptible task.

Claims

1. A method of managing at least one client computer program in a managed application environment comprising:

receiving a request from at least one of a plurality of client computer programs to begin a timer corresponding to an identified task executing within a particular thread of execution of said client computer program, wherein said identified task has been identified as a time-out susceptible task;

starting a timer in another separate thread of execution which corresponds to said request and said time-out susceptible task;

timing said time-out susceptible task; and

if said timer expires, performing a recovery action corresponding to said time-out susceptible task.

2. The method of claim 1, wherein said timer executes within a process separate from said time-out susceptible task.

3. The method of claim 1, wherein said recovery action comprises destroying said particular thread of execution.

4. The method of claim 1, wherein said recovery action comprises restarting said time-out susceptible task.

5. The method of claim 1, wherein said time-out sensitive task is part of a process and said recovery action comprises destroying said process.

6. The method of claim 5, further comprising:

restarting said process.

7. The method of claim 1, wherein said recovery action comprises forcing said client computer program to discontinue execution.

8. The method of claim 1, further comprising:

receiving a request from said client computer program to stop said timer.

9. A method of managing at least one client computer program in a managed application environment comprising:

identifying a process of a client computer program, wherein said process includes at least one time-out susceptible task executing in a particular thread of execution;

defining named timers corresponding to said time-out susceptible tasks;

receiving a request to enable one of said timers from said client computer program, wherein said request specifies a particular one of said timers corresponding to one of said time-out susceptible tasks which said client computer program has started to execute;

enabling said particular one of said timers;

creating a hash table entry for said particular one of said timers;

timing said time-out susceptible task, wherein said timer executes within a separate thread of execution; and

if said enabled timer expires, destroying said process in said client computer program.

10. The method of claim 9, wherein said timer executes in a process separate from said identified process.

11. The method of claim 9, further comprising:

restarting said process in said client computer program.

12. The method of claim 9, further comprising:

receiving a request to stop said particular one of said timers from said client computer program.

13. A system management agent for managing a plurality of client computer programs comprising:

a plurality of timers, each said timer corresponding to a time-out susceptible task of one of said computer programs executing within a designated thread of execution and having a predetermined maximum allowable time period;

an application programming interface accessible by the plurality of computer programs for receiving requests to enable and disable particular ones of said plurality of timers;

a configuration file associating said plurality of timers with said time-out susceptible tasks, and specifying said maximum allowable time periods, and defining one or more recovery mechanisms for each said time-out susceptible task;

a hash table for tracking enabled timers of said plurality of timers; and

a recovery component for coordinating said plurality of timers, said application programming interface, said configuration file, and said hash table, wherein said recovery component initiates one of said recovery mechanisms for time-out susceptible tasks having expired timers.

14. A machine-readable storage, having stored thereon a computer program having a plurality of code sections executable by a machine for causing the machine to perform the steps of:

receiving a request from at least one of a plurality of client computer programs to begin a timer corresponding to an identified task executing within a particular thread of execution of said client computer program, wherein said identified task has been identified as a time-out susceptible task;

starting a timer in another separate thread of execution which corresponds to said request and said time-out susceptible task;

timing said time-out susceptible task; and

if said timer expires, performing a recovery action corresponding to said time-out susceptible task.

15. The machine-readable storage of claim 14, wherein said timer executes within process separate from said time-out susceptible task.

16. The machine-readable storage of claim 14, wherein said recovery action comprises destroying said particular thread of execution.

17. The machine-readable storage of claim 14, wherein said recovery action comprises restarting said identified task.

18. The machine-readable storage of claim 14, wherein said task is part of a process and said recovery action comprises destroying said process.

19. The machine-readable storage of claim 18, further comprising:

restarting said process.

20. The machine-readable storage of claim 14, wherein said recovery action comprises forcing said client computer program to discontinue execution.

21. The machine-readable storage of claim 14, further comprising:

receiving a request from said client computer program to stop said timer.

22. A machine-readable storage, having stored thereon a computer program having a plurality of code sections executable by a machine for causing the machine to perform the steps of:

identifying a process of a client computer program, wherein said process includes at least one time-out susceptible task executing in a particular thread of execution;

defining named timers corresponding to said time-out susceptible tasks;

receiving a request to enable one of said timers from said client computer program, wherein said request specifies a particular one of said timers corresponding to one of said time-out susceptible tasks which said client computer program has started to execute;

enabling said particular one of said timers;

creating a hash table entry for said particular one of said timers;

timing said time-out susceptible task, wherein said timer executes within a separate thread of execution; and

if said enabled timer expires, destroying said process in said client computer program.

23. The machine-readable storage of claim 22, wherein said timer executes in a process separate from said identified process.

24. The machine-readable storage of claim 22, further comprising:

restarting said process in said client computer program.

25. The machine-readable storage of claim 22, further comprising:

receiving a request to stop said particular one of said timers from said client computer program.