Method and apparatus for monitoring and handling events for a collection of related threads in a data processing system

• US 6,842,898 B1
• Filed: 06/10/1999
• Issued: 01/11/2005
• Est. Priority Date: 06/10/1999
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Carlson, Michael Pierre, Ullmann, Lorin Evan
• Primary Examiner(s): An, Meng-Al T.
• Assistant Examiner(s): Tang, Kenneth
• Application Number:
  US09/329,456
• Time in Patent Office: 2,042 Days
• Field of Search: 718100-108, 709100-108, 709/229, 709/230
• US Class Current: 718/100
• 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/3017 where the computing system is implementing multitasking multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: G06F 9/5022 Mechanisms to release resources

Abstract

The present invention provides a method in a data processing system for monitoring a plurality of related threads. The plurality of related threads is polled for status information. Responsive to receiving the status information, A determination is made as to whether a thread within a plurality of related threads is active. Responsive to an absence of a determination that a thread within the plurality of related threads is active, a cleanup processes is initiated for the thread based on the status information.

Claims

1. A method in a data processing system for monitoring a plurality of related threads, the method comprising the data processing system implemented steps of:

polling the plurality of related threads for status information;

responsive to receiving the status information, determining whether a thread within a plurality of related threads is inactive; and

responsive to an occurrence of inactivity in a thread within the plurality of related threads in which the inactivity is due to an event, initiating cleanup processes based on the status information, wherein the event is at least one of an occurrence of a period of time or an error.

2. The method of claim 1 further comprising:

responsive to receiving the status information, storing the status information.

3. The method of claim 1, wherein the polling, determining, and initiating steps are performed by a single thread.

4. The method of claim 3, wherein the single thread is part of a class.

5. The method of claim 1, wherein the initiating stop comprises:

identifying active threads within the plurality of related threads;

identifying inactive threads within the plurality of related threads; and

terminating inactive threads.

6. The method of claim 1, wherein the plurality of related threads is a plurality of printer threads.

7. The method of claim 1, wherein the plurality of related threads is a plurality of video threads.

8. The method of claim 1, wherein the method is implemented in a virtual machine.

9. The method of claim 8, wherein the virtual machine is a Java virtual machine.

10. A data processing system for monitoring a plurality of related threads, the data processing system comprising:

polling means for polling the plurality of related threads for status information;

determining means, responsive to receiving the status information for determining whether a thread within a plurality of related threads is inactive; and

initialing means, responsive to an occurrence of inactivity in a thread within the plurality of related threads in which the inactivity is due to an event, for initiating cleanup processes based on the status information, wherein the event is at least one of an occurrence of a period of time or an error.

11. The data processing system of claim 10 further comprising:

storing means, responsive to receiving the status information, for storing the status information.

12. The data processing system of claim 10, wherein the polling, determining, and initiating means are preformed by a single thread.

13. The data processing system of claim 12, wherein the single thread is part of a class.

14. The date processing system of claim 10, wherein the initiating means comprises:

first identifying means for identifying active threads within the plurality of related threads;

second identifying means for identifying inactive threads within the plurality of related threads; and

terminating means for terminating inactive threads.

15. The data processing system of claim 10, wherein the plurality of related threads is a plurality of printer threads.

16. The data processing system of claim 10, wherein the plurality of related threads is a plurality of video threads.

17. The data processing system of claim 10, wherein the data processing system is implemented in a virtual machine.

18. The data processing system of claim 17, wherein the virtual machine is a Java virtual machine.

19. A computer program product in a computer readable medium for monitoring a plurality of related threads, the computer program product comprising:

first instructions for polling the plurality of related threads for status information;

second instructions, responsive to receiving the status information, for determining whether a thread within a plurality of related threads is inactive; and

third instructions, responsive to an occurrence of inactivity in a thread within the plurality of related threads in which the inactivity is due to an event, for initiating cleanup processes based on the status information, wherein the event is at least one of an occurrence of a period of time or an error.

20. The computer program product of claim 19 further comprising:

fourth instructions, responsive to receiving the status information, for storing the status information.

21. The computer program product of claim 19, wherein the polling, determining, and initiating instructions are performed by a single thread.

22. The computer program product of claim 21, wherein the single thread is part of a class.

23. The computer program product of claim 19, wherein the initiating instructions comprise:

first instructions for identifying active threads within the plurality of related threads;

second instructions for identifying inactive threads within the plurality of related threads; and

third instructions for terminating inactive threads.

24. The computer program product of claim 19, wherein the plurality of related threads is a plurality of printer threads.

25. The computer program product of claim 19, wherein the plurality of related threads is a plurality of video threads.

26. The computer program product of claim 19, wherein the computer program product is implemented in a virtual machine.

27. The computer program product of claim 26, wherein the virtual machine is a Java virtual machine.