System and method for monitoring threads in a clustered server architecture

• US 20060248283A1
• Filed: 04/29/2005
• Published: 11/02/2006
• Est. Priority Date: 04/29/2005
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: Stanev, Georgi, Galchev, Galin, Luik, Oliver
• Application Number:
  US11/118,019
• Publication Number:
  US 20060248283A1
• Time in Patent Office: Days
• US Class Current: 711/141
• CPC Class Codes: G06F 11/0715 in a system implementing multitasking multitasking per se G06F9/46
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating
• CPC Class Codes: G06F 11/1482 by means of middleware or OS functionality
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 11/362 Software debugging
• CPC Class Codes: G06F 2201/815 Virtual middleware or OS functionality using virtual machines to implement generic software techniques for error detection or fault masking G06F11/1484
• CPC Class Codes: G06F 2209/5016 Session
• CPC Class Codes: G06F 2209/5018 Thread allocation
• CPC Class Codes: G06F 9/5033 considering data affinity
• CPC Class Codes: G06F 9/505 considering the load

Abstract

A system and method are described for monitoring threads within an enterprise network. For example, one embodiment of the invention is a system for monitoring threads comprising: a plurality of worker nodes executing tasks in response to client requests, each worker node in the plurality using a plurality of threads to execute the tasks; a thread manager to retrieve information related to each of the threads and to transmit the information to a memory location shared by each of the worker nodes; a thread table to store the information related to the execution of each of the threads, the thread table accessible by one or more clients to provide access to the information by one or more users.

Claims

1. A system for monitoring threads comprising:

a plurality of worker nodes executing tasks in response to client requests, each worker node in the plurality using a plurality of threads to execute the tasks;

a thread manager to retrieve information related to each of the threads and to transmit the information to a memory location shared by each of the worker nodes;

a thread table to store the information related to the execution of each of the threads, the thread table accessible by one or more clients to provide access to the information by one or more users.

2. The system as in claim 1 wherein each of the worker nodes comprise a separate virtual machine.

3. The system as in claim 2 wherein each virtual machine is a Java virtual machine.

4. The system as in claim 1 further comprising:

a connection manager to distribute client requests to each of the worker nodes.

5. The system as in claim 1 further comprising:

a thread manager graphical user interface (“

GUI”

) to provide a graphical representation of the information related to each of the threads to an end user.

6. The system as in claim 5 wherein the thread manager GUI includes a plurality of rows, each representing a different thread, and a plurality of columns, each representing a different variable associated with each thread.

7. The system as in claim 1 wherein the information related to each of the threads includes a name associated with each thread and timing data associated with each thread.

8. The system as in claim 7 wherein the timing information includes a start time of the thread, a primary task executed by the thread, the time taken to perform the primary task, any sub-tasks associated with the primary task and the time taken to perform the sub-task.

9. A method for monitoring threads comprising:

using a plurality of threads to execute tasks on a plurality of worker nodes in response to client requests;

retrieving information related to each of the threads as the threads execute the plurality of tasks;

transmitting the information to a memory location shared by each of the worker nodes; and

storing the information related to the execution of each of the threads within a thread table, the thread table accessible by one or more clients to provide access to the information by one or more users.

10. The method as in claim 9 wherein each of the worker nodes comprise a separate virtual machine.

11. The method as in claim 10 wherein each virtual machine is a Java virtual machine.

12. The method as in claim 9 further comprising:

receiving requests from a plurality of clients; and

distributing the client requests to each of the worker nodes.

13. The method as in claim 9 further comprising:

generating a graphical representation of the information related to each of the threads for an end user.

14. The method as in claim 13 wherein the graphical representation includes a plurality of rows, each representing a different thread, and a plurality of columns, each representing a different variable associated with each thread.

15. The method as in claim 9 wherein the information related to each of the threads includes a name associated with each thread and timing data associated with each thread.

16. The method as in claim 15 wherein the timing information includes a start time of the thread, a primary task executed by the thread, the time taken to perform the primary task, any sub-tasks associated with the primary task and the time taken to perform the sub-task.

17. A machine-readable medium having program code stored thereon which, when executed by a machine, causes the machine to perform the operations of:

using a plurality of threads to execute tasks on a plurality of worker nodes in response to client requests;

retrieving information related to each of the threads as the threads execute the plurality of tasks;

transmitting the information to a memory location shared by each of the worker nodes; and

storing the information related to the execution of each of the threads within a thread table, the thread table accessible by one or more clients to provide access to the information by one or more users.

18. The machine-readable medium as in claim 17 wherein each of the worker nodes comprise a separate virtual machine.

19. The machine-readable medium as in claim 18 wherein each virtual machine is a Java virtual machine.

20. The machine-readable medium as in claim 19 comprising additional program code to cause the machine to perform the additional operations of:

receiving requests from a plurality of clients; and

distributing the client requests to each of the worker nodes.