Hierarchical debug

• US 8,490,064 B2
• Filed: 05/20/2005
• Issued: 07/16/2013
• Est. Priority Date: 05/21/2004
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Shrivastava, Sandeep, Inamdar, Rajendra, LeCompte, Ryan, Lindsay, R. Sean, Hess, Stephen, Mousseau, Richard
• Primary Examiner(s): MITCHELL, JASON D
• Application Number:
  US11/133,570
• Publication Number:
  US 20050273490A1
• Time in Patent Office: 2,979 Days
• Field of Search: 717124-135, 717151-161
• US Class Current: 717/130
• CPC Class Codes: G06F 11/0715 in a system implementing multitasking multitasking per se G06F9/46
• CPC Class Codes: G06F 11/079 Root cause analysis, i.e. error or fault diagnosis in a hardware test environment G06F11/22; in a software test environment G06F11/36
• CPC Class Codes: G06F 11/366 using diagnostics G06F11/0703 takes precedence

Abstract

Metadata can be used for determining or selecting debug points to activate for server software. The metadata can be used for selecting or logically grouping the debug point without requiring the selecting of debug points based upon package boundaries. The metadata can be used by the system to produce a select set of the debug activation information. This debug activation information can be used by a management unit to activate debug points in the server software.

Claims

1. A system comprising:

a diagnostic framework that executes on one or more microprocessors for debugging an application deployed on a server, wherein;

the application includes a set of join points, wherein each join point is associated with a diagnosis point associated with a plurality of diagnostic functions that collect diagnostic information as the application executes, and wherein the plurality of diagnostic functions are organized in nodes, said nodes organized in a hierarchy that includes a parent node and child nodes, and wherein

the server receives a plurality of requests that are processed by the application, wherein each request is associated with a diagnostic context that is used by the server to determine for which of the plurality of requests to collect diagnostic information;

metadata defined in a managed bean, wherein based on the plurality of requests received at the server, the metadata is used to select one or more of the nodes, wherein when the one or more of the nodes are selected, the plurality of diagnostic functions associated therewith are activated by the diagnostic framework;

wherein when the diagnostic framework activates the plurality of diagnostic functions the system;

determines the diagnostic context associated with the particular request, wherein based on the diagnostic context, the system generates metadata to select one or more of the nodes,

communicates the metadata to the diagnostic framework,

wherein the metadata specifies a selection of one or more of the child nodes, and wherein each selected child node activates the plurality of diagnostic functions associated with each selected child node, or

wherein the metadata specifies a selection of the parent node, and wherein when the parent node is selected, the plurality of diagnostic functions associated with the parent node is activated, including the plurality of diagnostic functions associated with the child nodes of said parent node; and

wherein, based on the selection, the diagnostic framework collects the diagnostic information as the particular request is executed by the application using the diagnostic functions of the selected nodes, and wherein the diagnostic information is stored on a non-transitory computer readable storage medium.

2. The system of claim 1, wherein the metadata is selected by a user from previously defined metadata.

3. The system of claim 1, wherein the metadata is defined in an object.

4. The system of claim 1, wherein the diagnosis point can be turned on without restarting the server software.

5. The system of claim 1, wherein the metadata is arranged in a hierarchical arrangement of nodes.

6. The system of claim 5, wherein when the parent node is enabled the children nodes of the parent node are enabled by default.

7. The system of claim 5, where some of the nodes are debug managed bean attributes.

8. The system of claim 5, wherein a diagnosis point can be associated with more than one node.

9. A method comprising:

providing a diagnostic framework debugger, that executes on one or more microprocessors, for debugging an application deployed on a server, wherein the application includes a set of join points, wherein each join point is associated with a diagnosis point associated with a plurality of diagnostic functions that collect diagnostic information as the application executes, and wherein the plurality of diagnostic functions are organized in nodes, said nodes organized in a hierarchy that includes a parent node and child nodes, and wherein

the server receives a plurality of requests that are processed by the application, wherein each request is associated with a diagnostic context that is used by the server to determine for which of the plurality of requests to collect diagnostic information;

defining metadata in a managed bean, wherein based on the plurality of requests received at the server, the metadata is used to select one or more of the nodes, wherein when one or more of the nodes are selected, the plurality of diagnostic functions associated therewith are activated by the diagnostic framework;

wherein activating the diagnostic functions comprises;

determining the diagnostic context associated with the request, wherein based on the diagnostic context, the system generates metadata to select one or more of the nodes

communicating the metadata to the diagnostic framework,

wherein the metadata specifies a selection of one or more of the child nodes, and wherein each selected child node activates the plurality of diagnostic functions associated with the selected child node, or

wherein the metadata specifies the selection of a parent node, wherein selecting the parent node activates the plurality of diagnostic functions associated with the parent node, including the plurality of diagnostic functions associated with the child nodes of said parent node; and

wherein, based on the selection, collecting the diagnostic information as the particular request is executed by the application using the diagnostic functions of the selected nodes.

10. The method of claim 9, wherein the metadata is selected by a user from previously defined metadata.

11. The method of claim 9, wherein the metadata is defined in an object.

12. The method of claim 9, wherein the diagnosis point can be turned on without restarting the server software.

13. The method of claim 9, wherein the metadata is arranged in a hierarchical arrangement of nodes.

14. The method of claim 13, wherein when the parent node is enabled the children nodes of the parent node are enabled by default.

15. The method of claim 13, where some of the nodes are debug managed bean attributes.

16. The method of claim 13, wherein a diagnosis point can be associated with more than one node.

17. A computer-readable storage medium comprising one or more sequences of instructions, which instructions, when executed by one or more processors, cause the one or more processors to:

provide a diagnostic framework, that executes on one or more microprocessors, for debugging an application deployed on a server, wherein

the application includes a set of join points, wherein each join point is associated with a diagnosis point associated with a plurality of diagnostic functions that collect diagnostic information as the application executes, and wherein the plurality of diagnostic functions are organized in nodes, said nodes organized in a hierarchy that includes a parent node and child nodes, and wherein

the server receives a plurality of requests that are processed by the application, wherein each request is associated with a diagnostic context that is used by the server to determine for which of the plurality of requests to collect diagnostic information;

define metadata in a managed bean, wherein based on the plurality of requests received at the server, the metadata is used to select one or more of the nodes;

wherein when one or more of the nodes are selected, the plurality of diagnostic functions associated therewith are activated by the diagnostic framework, and wherein activating the diagnostic functions comprises;

determining the diagnostic context associated with the request, wherein based on the diagnostic context, the system generates metadata to select one or more of the nodes

communicating the metadata to the diagnostic framework,

wherein the metadata specifies a selection of one or more of the child nodes, and wherein each selected child node activates the plurality of diagnostic functions associated with the selected child node, or

wherein the metadata specifies the selection of a parent node, wherein selecting the parent node activates the plurality of diagnostic functions associated with the parent node, including the plurality of diagnostic functions associated with the child nodes of said parent node; and

wherein, based on the selection, the instructions cause the one or more processors to collect the diagnostic information as the particular request is executed by the application using the diagnostic functions of the selected nodes.