System and method for determining unimportant probe locations by examination of byte code by identifying trivial methods

Abstract

A method, system, and computer-usable medium for determining unimportant probe locations by examination of byte code by identifying trivial methods according to a preferred embodiment of the present invention. In a preferred embodiment of the present invention, a management application identifies a first candidate location in byte code to instrument with a monitoring probe. The management application determines that the first candidate location links to a method of trivial importance and eliminates the first candidate location as a byte location to instrument. The management application identifies a second candidate location in byte code to instrument with a monitoring probe. The management application determines that the second candidate location links to a method of importance and instruments the second candidate location with the monitoring probe.

Description

BRIEF DESCRIPTION OF THE FIGURES

The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further purposes and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying figures, wherein:

FIG. 1 illustrates an exemplary network in which a preferred embodiment of the present invention may be implemented;

FIG. 2 depicts an exemplary server in which a preferred embodiment of the present invention may be implemented;

FIG. 3 illustrates a relationship between a Java Virtual Machine (JVM), a monitoring agent, and a transaction running on a system according to a preferred embodiment of the present invention; and

FIG. 4 is a high-level logical flowchart depicting an exemplary method for determining unimportant probe locations by examination of byte code by identifying trivial methods according to a preferred embodiment of the present invention.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT

With reference to FIG. 1, a computer system 100 for a business entity is connected to the Internet 102 in order to provide computer services online. The website of the business entity is accessible to various online users 104.

In the presently preferred embodiment, Java 2 Platform Enterprise Edition (J2EE) is used on computer system 100. J2EE is a platform-independent, JAVA-centric environment from Sun Microsystems for developing, building and deploying Web-based enterprise applications online. The J2EE platform consists of a set of services, APIs, and protocols that provide the functionality for developing multitiered, Web-based applications. At the client level, J2EE supports pure HTML, as well as Java applets or applications. Enterprise JavaBeans (EJBs) provide another layer where the platform's logic is stored. Within computer system 100, Web server 106 is configured to communicate over the Internet, as well as within the intranet of system 100; application server 108 is only connected to communicate within the intranet, but can access application database 112. In addition to other programs and processes that exist on these servers, each of server 106, 108 contains a copy of Java Virtual Machine (JVM) 114 and monitoring program 116, which will be discussed further below. One of ordinary skill in the art will recognize that many other configurations are possible in the disclosed intranet. For example, the web server and the application server can be on a single machine. Conversely, there may be a number of both web servers and application servers; there may also be separate database servers if the situation required it.

Referring to FIG. 2, a block diagram of a data processing system that may be implemented as a server, such as servers 106, 108 in FIG. 1, is depicted in accordance with a preferred embodiment of the present invention. Data processing system 200 may be a symmetric multiprocessor (SMP) system including a plurality of processors 202 and 204 connected to system bus 206. Alternatively, a single processor system may be employed. Also connected to system bus 206 is memory controller/cache 208, which provides an interface to local memory 209. I/O bus bridge 210 is connected to system bus 206 and provides an interface to I/O bus 212. Memory controller/cache 208 and I/O bus bridge 210 may be integrated as depicted.

Peripheral component interconnect (PCI) bus bridge 214 connected to I/O bus 212 provides an interface to PCI local bus 216. A number of modems may be connected to PCI local bus 216. Typical PCI bus implementations will support four PCI expansion slots or add-in connectors. Communications links to users 104 in FIG. 1 may be provided through modem 218 and network adapter 220 connected to PCI local bus 216 through add-in connectors.

Additional PCI bus bridges 222 and 224 provide interfaces for additional PCI local buses 226 and 228, from which additional modems or network adapters may be supported. In this manner, data processing system 200 allows connections to multiple network computers. A memory-mapped graphics adapter 230 and hard disk 232 may also be connected to I/O bus 212 as depicted, either directly or indirectly.

Those of ordinary skill in the art will appreciate that the hardware depicted in FIG. 2 may vary. For example, other peripheral devices, such as optical disk drives and the like, also may be used in addition to or in place of the hardware depicted. The depicted example is not meant to imply architectural limitations with respect to the present invention.

With reference to FIG. 3, an overview the relationship between an application 310, a copy of the Java Virtual Machine (JVM) 320, and a monitoring agent 330 is shown. A bi-directional interface exists between JVM 320 and monitoring agent 330. Monitoring agent 330 contains injector 332 (which injects byte codes or hooks into applications), registry 334 (which contains a registry of all enabled probes), hooks 336 (which contain the logic to manage the execution of probes), and probes 338. Probes can be enabled or disabled by management application 340. Exemplary application 310 contains servlet 311, which invokes Enterprise JavaBeans (EJBs) 312, 314. In turn EJB 314 invokes further EJBs 316, 318. When application 310 is compiled by the JVM, the interface between JVM 320 and monitoring agent 330 allows injector 332 to inject special byte codes 350 into the components 311, 312, 314, 316, 318 of application class 310 to form managed application 310′. Note that each of the components 311′, 312′, 314′, 316′, 318′ of managed application 310′ contains inserted byte codes 350. These byte codes 350 correspond to hooks 336; when managed application 310′ executes, hooks 336 will interface with registry 334 and cause the desired probes 338 to execute.

FIG. 4 is a high-level logical flowchart diagram illustrating an exemplary method for determining unimportant probe locations by examination of byte code to identifying trivial methods according to a preferred embodiment of the present invention. The process begins at step 400 and proceeds to step 402, which illustrates the startup of computer system 100 and the loading of classes. The process continues to step 404, which depicts computer system 100 invoking management application 340 to insert probes into the class byte code of each class loaded. The process continues to step 406, which illustrates management application 340 examining each object's method to determine if the method includes performance data of interest to management application 340.

The process proceeds to step 408, which illustrates management application 340 determining if the examined method is characteristic of a method with deterministic or short computation times. In a preferred embodiment of the present invention, management application 340 dynamically detects certain characteristics of the target method before inserting instrumentation code. One such type of unimportant probe location is known as “trivial methods” or methods that have deterministic and short computation times. These methods are ones without (but not limited to) subsequent method invocations (e.g., method calls or recursion), branch conditions (e.g., if blocks), or loops (e.g., for loops, while loops, do-while loops).

If the examined method is characteristic of a method with deterministic or short computation times, the process continues to step 412. If the examined method is not characteristic of a method with deterministic or short computation times, the process continues to step 410, which depicts management application 340 inserting a monitoring probe (e.g., probes 338) into the method's byte code. The process proceeds to step 412, which illustrates management application 340 examining the next class/method in application 310. The process returns to step 408 and proceeds in an iterative fashion.

As discussed, the present invention includes a method, system, and computer-usable medium for determining unimportant probe locations by examination of byte code by identifying trivial methods according to a preferred embodiment of the present invention. In a preferred embodiment of the present invention, a management application identifies a first candidate location in byte code to instrument with a monitoring probe. The management application determines that the first candidate location links to a method of trivial importance and eliminates the first candidate location as a byte location to instrument. The management application identifies a second candidate location in byte code to instrument with a monitoring probe. The management application determines that the second candidate location links to a method of importance and instruments the second candidate location with the monitoring probe.

It should be understood that at least some aspects of the present invention may alternatively be implemented in a computer-usable medium that contains a program product. Programs defining functions in the present invention can be delivered to a data storage system or a computer system via a variety of signal-bearing media, which include, without limitation, non-writable storage media (e.g., CD-ROM), writable storage media (e.g., hard disk drive, read/write CD-ROM, optical media), system memory such as, but not limited to Random Access Memory (RAM), and communication media, such as computer and telephone networks, including Ethernet, the Internet, wireless networks, and like network systems. It should be understood, therefore, that such signal-bearing media when carrying or encoding computer readable instructions that direct method functions in the present invention represent alternative embodiments of the present invention. Further, it is understood that the present invention may be implemented by as a system having means in the form of hardware, software, or a combination of software and hardware as described herein or their equivalent.

While the present invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention. Furthermore, as utilized in the specification and the appended claims, the term “computer” or “system” or “computer system” or “computing device” includes any data processing system including, but not limited to, personal computers, servers, workstations, network computers, main frame computers, routers, switches, personal digital assistants (PDAs), telephones, and any other system capable of processing, transmitting, receiving, capturing, and/or storing data.

Claims

1. A method for monitoring a transaction, said method comprising: identifying a first candidate location in byte code to instrument with a monitoring probe;determining that said first candidate location links to a method of trivial importance;eliminating said first candidate location as a byte location to instrument;identifying a second candidate location in byte code to instrument with a monitoring probe;determining that the second candidate location links to a method of importance; andinstrumenting said second candidate location with said monitoring probe.

2. The method according to claim 1, wherein said method of trivial importance is a method with deterministic computations.

3. The method according to claim 1, wherein said method of trivial importance is a method with short computation times.

4. The method according to claim 1, wherein said method of trivial importance is a method without subsequent method invocations, branch conditions, or loops.

5. A system comprising: a processor;a databus coupled to said processor; anda computer-usable medium embodying computer program code, said computer-usable medium being coupled to said databus, said computer program code comprising instructions executable by said processor and configure for: identifying a first candidate location in byte code to instrument with a monitoring probe;determining that said first candidate location links to a method of trivial importance;eliminating said first candidate location as a byte location to instrument;identifying a second candidate location in byte code to instrument with a monitoring probe;determining that the second candidate location links to a method of importance; andinstrumenting said second candidate location with said monitoring probe.

6. The system according to claim 5, wherein said method of trivial importance is a method with deterministic computations.

7. The system according to claim 5, wherein said method of trivial importance is a method with short computation times.

8. The system according to claim 5, wherein said method of trivial importance is a method without subsequent method invocations, branch conditions, or loops.

9. A computer-usable medium embodying computer program code, said computer program code comprising computer-executable instructions configured for: identifying a first candidate location in byte code to instrument with a monitoring probe;determining that said first candidate location links to a method of trivial importance;eliminating said first candidate location as a byte location to instrument;identifying a second candidate location in byte code to instrument with a monitoring probe;determining that the second candidate location links to a method of importance; andinstrumenting said second candidate location with said monitoring probe.

10. The computer-usable medium according to claim 9, wherein said method of trivial importance is a method with deterministic computations.

11. The computer-usable medium according to claim 9, wherein said method of trivial importance is a method with short computation times.

12. The computer-usable medium according to claim 9, wherein said method of trivial importance is a method without subsequent method invocations, branch conditions, or loops.