Method and system of associating a runtime event with a component

Patent metadata

Field	Value
Publication number	US-9329969-B2
Application number	US-21196108-A
Country	US
Kind code	B2
Filing date	Sep 17, 2008
Priority date	Sep 19, 2007
Publication date	May 3, 2016
Grant date	May 3, 2016

Abstract

A method and a system of associating a runtime event with a component. The method includes catching the runtime event; catching the context of the current running environment and determining the current component based on said context; and getting the associating policy of current component and determining the responsible component associated with said runtime event based on said associating policy.

First claim

What is claimed is:

1. A method for determining a computing component responsible for associating a runtime event with a component of a computing system, comprising: assigning an associating policy label to each available component of a computing system, said associating policy label indicating an associating policy associating a runtime event with said component; and the computing system automatically performing runtime steps of: catching a runtime event during execution; identifying a context of a current running environment and determining a current component handling the runtime event based on said context; and obtaining the associating policy of the current component determined to be handling the runtime event, wherein the current component is in a first application and the runtime event is in a second application that is different from the first application; determining a responsible component associated with said runtime event based on said associating policy; and providing an indication of the responsible component for analysis, wherein assigning an associating policy label comprises at least one of: attaching the associating policy label to the available component; storing at least a set of associating policy labels of the available component in a policy storage device; and providing a dedicated API to the available component.

2. The method according to claim 1 , wherein steps of identifying a context of a current running environment and determining a current component based on said context include at least one of examining a snapshot of an execution stack and examining the execution log, and wherein said determining the current component is based on said snapshot or said log.

3. The method according to claim 1 , further comprising:
performing one of loading the associating policy label and the available component together to the execution stack and recording the associating policy label and the available component into the execution log when the available component is called during execution; and
wherein the step of obtaining an associating policy of the current component further comprises retrieving said attached associating policy label from said context.

4. The method according to claim 1 , further comprising:
storing at least a set of associating policy labels of each available component in a policy storage device; and
the step of obtaining an associating policy of the current component further comprises reading said associating policy label from the policy storage device.

5. The method according to claim 1 , wherein the step of obtaining an associating policy of the current component further comprises calling a dedicated API to obtain said associating policy.

6. The method according to claim 1 , further comprising steps of:
storing a track of said running environment; and
analyzing recursively the context of the current running environment based on the track to determine the responsible component associated with said runtime event.

7. The method according to claim 3 wherein said associating policy label is one or more of the following: Parent, Self, Caller, Classloader, Common, Allocater, and Boundary, and wherein
when the policy label is Self, the current component is determined as the responsible component;
when the policy label is Parent, a parent component creating a thread is determined as the responsible component;
when the policy label is Caller, a caller component calling the current component is determined as the responsible component;
when the policy label is Classloader, a system component loading the current component is determined as the responsible component;
when the policy label is Common, a common service component providing common services is determined as the responsible component;
when the policy label is Allocater, an allocater associated with resources is determined as the responsible component; and
when the policy label is Boundary, a top component on the execution stack is determined as the responsible component.

8. The method according to claim 1 , further comprising:
upon the context of the current running environment being identified, determining whether at least one of the current component or the associating policy has changed from that of a preceding event, and if so, determining the responsible component associated with said runtime event.

9. The method according to claim 1 , wherein providing an indication comprises at least one of updating statistics on the association of the responsible component with the runtime event in a statistics accounting pool and displaying an association relationship between the runtime event and the responsible component.

10. The method according to claim 1 , wherein the runtime event is caught by one of actively sampling and passively being triggered by the event.

11. A non-transitory computer storage medium storing a program of instructions for causing a computer to perform a method for determining a computing component responsible for associating a runtime event with a component of a computing system, the method comprising: assigning an associating policy label to each available 5 component of a computing system, said associating policy label indicating an associating policy associating a runtime event with said component; and the computing system automatically performing runtime steps of: catching a runtime event during execution; identifying a context of a current running environment and determining a current component handling the runtime event based on said context; and obtaining the associating policy of the current component determined to be handling the runtime event, wherein the current component is in a first application and the runtime event is in a second application that is different from the first application; determining a responsible component associated with said runtime event based on said associating policy; and providing an indication of the responsible component for analysis, wherein assigning an associating policy label comprises at least one of: attaching the associating policy label to the available component; storing at least a set of associating policy labels of the available component in a policy storage device; and providing a dedicated API to the available component.

12. The non-transitory computer storage medium according to claim 11 , wherein said identifying a context further comprises at least one of catching a snapshot of the execution stack, and updating log information based on a current program execution situation, and wherein said determining the current component is based on one of said snapshot and said log.

13. The non-transitory computer storage medium according to claim 11 , further comprising:
loading the associating policy label and the available component together to the execution stack when the available component is called during execution,
wherein the step of obtaining an associating policy of the currently component further comprises retrieving said attached associating policy label from the context of said running environment.

14. The non-transitory computer storage medium according to claim 11 , further comprising storing an associating policy label for each available component, wherein the step of obtaining an associating policy of the current component further comprises reading said associating policy label from the policy storage device.

15. The non-transitory computer storage medium according to claim 11 , wherein said step of obtaining an associating policy of the current component further comprises reading a dedicated API to obtain said policy.

16. The non

Assignees

• Hargrave Bentley John
• Li Xin Hui
• Li Ying
• Liu Tian Cheng
• Qiu Jie
• Teng Qi Ming
• Tracey William J
• Wood Iii David Alvra
• IBM

Inventors

• Hargrave Bentley John
• Li Xin Hui
• Li Ying
• Liu Tian Cheng
• Qiu Jie
• Teng Qi Ming
• Tracey William J
• Wood Iii David Alvra

Classifications

• G06F11/3476

  Data logging (G06F11/14, G06F11/2205 take precedence) · CPC title

• G06F8/20

  Software design · CPC title

• G06F11/3419

  by assessing time · CPC title

• G06F2209/543

  Local · CPC title

• G06F9/542

  Event management; Broadcasting; Multicasting; Notifications · CPC title